wavexis_set_cache_disabled
Enable or disable browser cache.
This record as markdown: /tools/wavexis-mcp/wavexis-set-cache-disabled.md
What wavexis_set_cache_disabled does on Pypi:wavexis
AI agents invoke wavexis_set_cache_disabled to trigger actions in Pypi:wavexis. 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 wavexis_set_cache_disabled is rated High
This tool toggles a browser-level setting (cache enabled/disabled) which affects how the browser operates during a session. It's not a simple read, it modifies browser behavior. It's not destructive or financial, but it does trigger a change in browser execution environment, fitting the Execute category. Misuse could cause degraded performance or unexpected behavior during automation sessions.
From the tool's definition 'Enable or disable browser cache' — modifies browser runtime configuration/state
Attacks that exploit this kind of access
The rule that runs wavexis_set_cache_disabled safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pypi:wavexis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wavexis_set_cache_disabled, this is the rule to start with:
wavexis_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 Pypi:wavexis, apply this rule, and every wavexis_set_cache_disabled call is checked against it from then on.
Questions about wavexis_set_cache_disabled
Enable or disable browser cache. It is categorised as a Execute tool in the Pypi:wavexis MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pypi:wavexis MCP server in PolicyLayer and add a rule for wavexis_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 Pypi:wavexis. Nothing to install.
wavexis_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 wavexis_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 wavexis_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.
wavexis_set_cache_disabled is provided by the Pypi:wavexis MCP server (MathiasPaulenko/wavexis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Pypi:wavexis, and thousands of servers like it.
Across the catalogue