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

WHAT IT DOES

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

AI agents invoke kinsta.cdn.clear-cache 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.cdn.clear-cache needs a policy

Clearing a CDN cache is an operational action that triggers an external infrastructure operation (invalidating cached content), causing cache misses and potential performance impact. It doesn't permanently delete data (content is re-cached from origin) but it does trigger an external operation with real effects, placing it in Execute.

From the tool's definition Clear the CDN cache for an environment

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

kinsta.cdn.clear-cache Rate-limited

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

FAQ

Questions about kinsta.cdn.clear-cache

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

Clear the CDN 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.cdn.clear-cache? +

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

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

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

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

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

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

kinsta.cdn.clear-cache 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.