# 4.10 Remove Request Value

#### 🧾 Overview

The **Remove Request Value** module allows you to strip unwanted or sensitive arguments from requests before they reach your backend servers.\
This can help prevent misuse of hidden features, developer flags, or outdated query parameters.

***

#### 🛠️ How It Works

You define:

* **Page Path** – The URL to monitor (e.g., `/checkout`, `/api/data`)
* **Argument Content** – The name of the parameter (e.g., `debug`, `token`, `env`) to remove from the request

If a request includes the defined path **and** contains the specified argument, that argument is **silently removed**.

***

#### ⚙️ How to Add a Rule

1. Navigate to **Security Rules > Remove Request Value**
2. Click **Create Redactable Argument**
3. Fill in:
   * `Enter Page Path`: the full or partial URL where the rule applies
   * `Enter Argument Content`: the parameter name to strip
4. Click **Redact / Red Et**
5. The argument will be removed from all future requests to that path

<figure><img src="/files/XqGLjy5PiC8WvNFkVjLD" alt=""><figcaption></figcaption></figure>

***

#### ✅ Example

**Request Before:**\
`GET /submit?email=test@example.com&debug=true`

**Rule:**

* Page Path: `/submit`
* Argument Content: `debug`

**Request After:**\
`GET /submit?email=test@example.com`\
→ `debug` parameter is removed

***

#### 🔐 Why It Matters

Removing unnecessary or dangerous parameters helps:

* Prevent abuse of undocumented features
* Eliminate developer/debug switches from production
* Clean up noisy or irrelevant input before processing

***

🎯 **Remove Request Value ensures clean, secure, and predictable request handling — directly at the edge.**


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.shieldsguard.com/getting-started/4.-security-rules/4.10-remove-request-value.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.