Inspect specific cache entries in Magento 2
AI agents call cache-view to retrieve information from Magento 2 Development MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs inspection/viewing of cache entries, which is a non-destructive retrieval operation with no side effects. It aligns with the Read category definition of retrieving or querying data without side effects. The low severity reflects minimal blast radius—viewing cache entries cannot modify system state or cause harm even if misused by an agent.
From the tool's definition Tool name 'cache-view' and description 'Inspect specific cache entries in Magento 2' indicate a read-only operation that retrieves and displays cache data without modification.
Documented attack patterns abuse exactly the kind of access cache-view 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-view:
{
"version": "1",
"default": "deny",
"tools": {
"cache-view": {}
}
} cache-view is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Inspect specific cache entries in Magento 2. It is categorised as a Read tool in the Magento 2 Development MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Magento 2 Development MCP Server MCP server in PolicyLayer and add a rule for cache-view: 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-view is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the cache-view 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-view. 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-view 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.