get_cache_report
Get CDN cache report (requires Website Turbo)
This record as markdown: /tools/cbrown35-20i-mcp/get-cache-report.md
What get_cache_report does on 20i MCP Server
AI agents call get_cache_report to retrieve information from 20i MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_cache_report is rated Low
This tool retrieves analytics or diagnostic information about CDN cache performance. It queries data without side effects, making it a Read operation. The blast radius is low since it only exposes cached content metrics and diagnostic information, not sensitive credentials or payment data, and does not modify any system state.
From the tool's definition Tool name 'get_cache_report' and description 'Get CDN cache report' indicate retrieval of existing data with no modification, deletion, or execution of commands.
Attacks that exploit this kind of access
The rule that runs get_cache_report safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 20i MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_cache_report, this is the rule to start with:
get_cache_report is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 20i MCP Server, apply this rule, and every get_cache_report call is checked against it from then on.
Questions about get_cache_report
Get CDN cache report (requires Website Turbo). It is categorised as a Read tool in the 20i MCP Server MCP Server, which means it retrieves data without modifying state.
Register the 20i MCP Server MCP server in PolicyLayer and add a rule for get_cache_report: 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 20i MCP Server. Nothing to install.
get_cache_report 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 get_cache_report 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 get_cache_report. 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.
get_cache_report is provided by the 20i MCP Server MCP server (cbrown35/20i-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 20i MCP Server, and thousands of servers like it.
This server
Across the catalogue