Here's an example of adding a rule:
* Step 1: enter the desired domain that the rule is to be applied. The domain must be included as it is a part of the pattern, and the rule will only be effective for domains that match this pattern.
* Step 2: enter the pattern that will be checked to determine which URLs the rule should apply to. You can use regular expressions to form this pattern to allow flexibility in searching.
* Step 3: enter the pattern type, which currently only supports URL patterns.
* Step 4, for redirection only, enter the rewrite pattern, which is a part of the pattern and will override the corresponding content in the rewrite information.
* Step 5, for redirection only, enter the rewrite information, which is the text that will replace the matched content based on the rewrite pattern.
* Step 6, select the rule type that will be performed using the pattern. Currently, only redirection/rewrite and denial are supported. Various options change the return code received by the browser.
* Lastly, click "**Submit**" to complete adding the rule.
---
# 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://deeper-network-inc.gitbook.io/deeper-connect-knowledge-base/atom-os-functions/security/customized-https-rules/add-rule.md?ask=
```
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.