kinsta.edge-cache.clear · Kinsta MCP Server MCP

WHAT IT DOES

What kinsta.edge-cache.clear does on Kinsta MCP Server

AI agents invoke kinsta.edge-cache.clear to trigger actions in Kinsta 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 kinsta.edge-cache.clear needs a policy

Clearing edge cache is an operational action that triggers a side effect on external infrastructure (CDN/edge nodes). It is not purely destructive (cache will be repopulated) nor a simple write, but rather executes an infrastructure operation. Misuse could temporarily degrade site performance by forcing cache repopulation, but effects are transient and reversible.

From the tool's definition 'Clear the edge cache for an environment' — triggers an external cache invalidation operation on Kinsta infrastructure

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

kinsta.edge-cache.clear Rate-limited

kinsta.edge-cache.clear 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": {
    "kinsta.edge-cache.clear": {
      "limits": [
        {
          "counter": "kinsta.edge-cache.clear_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 Kinsta MCP Server, so you can run agents against it safely.

FAQ

Questions about kinsta.edge-cache.clear

What does the kinsta.edge-cache.clear tool do? +

Clear the edge cache for an environment. Returns an operation_id. It is categorised as a Execute tool in the Kinsta 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 kinsta.edge-cache.clear? +

Register the Kinsta MCP Server MCP server in PolicyLayer and add a rule for kinsta.edge-cache.clear: 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 Kinsta MCP Server. Nothing to install.

What risk level is kinsta.edge-cache.clear? +

kinsta.edge-cache.clear is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit kinsta.edge-cache.clear? +

Yes. Add a rate_limit block to the kinsta.edge-cache.clear 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 kinsta.edge-cache.clear completely? +

Set action: deny in the PolicyLayer policy for kinsta.edge-cache.clear. 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 kinsta.edge-cache.clear? +

kinsta.edge-cache.clear is provided by the Kinsta MCP Server MCP server (jacob-hartmann/kinsta-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.