Toggle edge cache defensive mode for a site.
AI agents use pressable_toggle_edge_cache_defensive_mode to create or update resources in Pressable MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pressable MCP Server environment.
Toggling a setting is a reversible configuration change — it can be toggled back — so it falls under Write rather than Execute or Destructive. Misuse could degrade site performance or caching behavior, but the action is reversible, making severity medium.
From the tool's definition Toggle edge cache defensive mode for a site
Attacks that exploit this kind of access
Toggle edge cache defensive mode for a site. It is categorised as a Write tool in the Pressable MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pressable MCP Server MCP server in PolicyLayer and add a rule for pressable_toggle_edge_cache_defensive_mode: 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 Pressable MCP Server. Nothing to install.
pressable_toggle_edge_cache_defensive_mode is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the pressable_toggle_edge_cache_defensive_mode 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 pressable_toggle_edge_cache_defensive_mode. 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.
pressable_toggle_edge_cache_defensive_mode is provided by the Pressable MCP Server MCP server (pcwprops/pressable-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →