pressable_purge_edge_cache · Pressable MCP Server MCP

WHAT IT DOES

What pressable_purge_edge_cache does on Pressable MCP Server

AI agents invoke pressable_purge_edge_cache to trigger actions in Pressable MCP Server. 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 IT NEEDS A POLICY

Why pressable_purge_edge_cache needs a policy

Cache purging is an irreversible operation that clears all cached content at the edge, forcing re-fetching from origin. While it doesn't delete source data, it does have side effects on site performance and external infrastructure state. It falls under Execute as it triggers an external operation (cache invalidation) rather than simply reading or writing persistent data.

From the tool's definition 'Purge the edge cache for a specific site' — purging a cache is an operational action that clears cached content and triggers re-fetching, affecting external CDN/edge state

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pressable_purge_edge_cache Rate-limited

pressable_purge_edge_cache 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pressable_purge_edge_cache": {
      "limits": [
        {
          "counter": "pressable_purge_edge_cache_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Pressable MCP Server, so you can run agents against it safely.

FAQ

Questions about pressable_purge_edge_cache

What does the pressable_purge_edge_cache tool do? +

Purge the edge cache for a specific site. It is categorised as a Execute tool in the Pressable MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on pressable_purge_edge_cache? +

Register the Pressable MCP Server MCP server in PolicyLayer and add a rule for pressable_purge_edge_cache: 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.

What risk level is pressable_purge_edge_cache? +

pressable_purge_edge_cache is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit pressable_purge_edge_cache? +

Yes. Add a rate_limit block to the pressable_purge_edge_cache 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.

How do I block pressable_purge_edge_cache completely? +

Set action: deny in the PolicyLayer policy for pressable_purge_edge_cache. 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.

What MCP server provides pressable_purge_edge_cache? +

pressable_purge_edge_cache 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.