AI agents call get_cache_stats to retrieve information from Web Scraper without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns cache statistics (hits, misses, size) which are informational metrics. It has no side effects, does not modify data, does not execute code or commands, and does not move money or irreversibly delete anything. It is a straightforward data retrieval operation, fitting the 'Read' category with low severity since exposing cache statistics poses minimal security risk.
From the tool's definition Tool name 'get_cache_stats' and description 'Get response cache statistics (hits, misses, size)' indicate a read-only operation that retrieves metrics about cache performance without modifying any data or triggering external actions.
Documented attack patterns abuse exactly the kind of access get_cache_stats gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Web Scraper, and nothing reaches the server without passing your rules. This is the rule we recommend for get_cache_stats:
{
"version": "1",
"default": "deny",
"tools": {
"get_cache_stats": {}
}
}get_cache_stats 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.
Get response cache statistics (hits, misses, size). It is categorised as a Read tool in the Web Scraper MCP Server, which means it retrieves data without modifying state.
Register the Web Scraper MCP server in PolicyLayer and add a rule for get_cache_stats: 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 Web Scraper. Nothing to install.
get_cache_stats 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_stats 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_stats. 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_stats is provided by the Web Scraper MCP server (imyourboyroy/webscrapertoolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Web Scraper, 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.
62 Web Scraper tools catalogued and risk-classified — across an index of 43,000+ MCP servers.