cache-flush · Magento 2 Development MCP Server MCP

WHAT IT DOES

What cache-flush does on Magento 2 Development MCP Server

AI agents invoke cache-flush 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.

THE RISK

High Risk

Why cache-flush needs a policy

Cache flushing triggers an external operation that clears cached data. While it doesn't permanently destroy source data, it causes cache invalidation and forces regeneration, which can affect system performance and availability. It's not purely destructive (caches rebuild) but it does execute an operation with real side effects beyond simple reads or writes.

From the tool's definition Flush specific Magento 2 cache types or all caches

Documented attack patterns abuse exactly the kind of access cache-flush gives an agent:

POLICY

How to control cache-flush

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-flush:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cache-flush": {
      "limits": [
        {
          "counter": "cache-flush_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

cache-flush 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.

Create a free account and register Magento 2 Development MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Magento 2 Development MCP Server tools

Execute cache-clean Clear specific Magento 2 cache types or all caches Execute sys-cron-run Run Magento 2 cron jobs Execute db-query Execute SQL queries directly on Magento 2 database Execute setup-di-compile Compile Magento 2 dependency injection configuration Execute setup-static-content-deploy Deploy Magento 2 static content and assets Execute setup-upgrade Run Magento 2 setup upgrade to update database schema and data Write cache-disable Disable specific Magento 2 cache types Write cache-enable Enable specific Magento 2 cache types

All 29 Magento 2 Development MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Magento 2 Development MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about cache-flush

What does the cache-flush tool do? +

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

How do I enforce a policy on cache-flush? +

Register the Magento 2 Development MCP Server MCP server in PolicyLayer and add a rule for cache-flush: 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.

What risk level is cache-flush? +

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

Can I rate-limit cache-flush? +

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

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

cache-flush 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.

Enforce policy on every Magento 2 Development MCP Server tool call.

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.

CHECK YOUR STACK →

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.