Clear specific Magento 2 cache types or all caches
AI agents invoke cache-clean to trigger actions in Magento 2 Development 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.
Clearing caches triggers an external operation that affects application state (cache invalidation), which can impact performance and availability. It is not purely destructive (data is not permanently lost), but it executes an action with real side effects on the running system. Misuse could degrade application performance by forcing cache rebuilds or temporarily disrupting service.
From the tool's definition Clear specific Magento 2 cache types or all caches
Documented attack patterns abuse exactly the kind of access cache-clean gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Magento 2 Development MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for cache-clean:
{
"version": "1",
"default": "deny",
"tools": {
"cache-clean": {
"limits": [
{
"counter": "cache-clean_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}cache-clean 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.
Free to start. No card required.
Clear specific Magento 2 cache types or all caches. It is categorised as a Execute tool in the Magento 2 Development MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Magento 2 Development MCP Server MCP server in PolicyLayer and add a rule for cache-clean: 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 Magento 2 Development MCP Server. Nothing to install.
cache-clean 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 cache-clean 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 cache-clean. 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.
cache-clean is provided by the Magento 2 Development MCP Server MCP server (elgentos/magento2-dev-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Magento 2 Development MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
29 Magento 2 Development MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.