set_cache_disabled
Toggles the browser cache for the page via CDP Network.setCacheDisabled.
This record as markdown: /tools/1600822305-js-reverse-mcp/set-cache-disabled.md
What set_cache_disabled does on Js Reverse
AI agents invoke set_cache_disabled 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 set_cache_disabled is rated High
This tool executes a browser control action via the Chrome DevTools Protocol, modifying the browser's runtime caching behavior. It doesn't read data, persistently write or delete data, or involve financial operations — it triggers an external operation (toggling cache) whose effect depends on the argument passed. The blast radius is low as it only affects the current browser session's cache behavior.
From the tool's definition Toggles the browser cache for the page via CDP Network.setCacheDisabled
Attacks that exploit this kind of access
The rule that runs set_cache_disabled 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 set_cache_disabled, this is the rule to start with:
set_cache_disabled 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 set_cache_disabled call is checked against it from then on.
Questions about set_cache_disabled
Toggles the browser cache for the page via CDP Network.setCacheDisabled. 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 set_cache_disabled: 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.
set_cache_disabled 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 set_cache_disabled 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 set_cache_disabled. 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.
set_cache_disabled 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