add_network_rule
Adds a network interception rule (replaces the old intercept_requests).
This record as markdown: /tools/1600822305-js-reverse-mcp/add-network-rule.md
What add_network_rule does on Js Reverse
AI agents invoke add_network_rule to trigger actions in Js Reverse. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why add_network_rule is rated High
This tool modifies browser network behavior by adding interception rules, which can intercept, modify, or block network requests in real-time. This constitutes triggering external operations with effects dependent on arguments — it can redirect traffic, alter requests/responses, or block communications. Misuse could allow an AI agent to intercept sensitive data, modify API calls, or disrupt web application behavior.
From the tool's definition Adds a network interception rule (replaces the old intercept_requests)
Attacks that exploit this kind of access
The rule that runs add_network_rule safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Js Reverse, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_network_rule, this is the rule to start with:
add_network_rule stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Js Reverse, apply this rule, and every add_network_rule call is checked against it from then on.
Questions about add_network_rule
Adds a network interception rule (replaces the old intercept_requests). It is categorised as a Execute tool in the Js Reverse MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Js Reverse MCP server in PolicyLayer and add a rule for add_network_rule: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Js Reverse. Nothing to install.
add_network_rule is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the add_network_rule rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for add_network_rule. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
add_network_rule is provided by the Js Reverse MCP server (1600822305/js-reverse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Js Reverse, and thousands of servers like it.
Across the catalogue