Force refresh the documentation cache from all three sources (getrecon.xyz, book.getrecon.xyz, getrecon.substack.com). Rate limited to once per 60 seconds.
AI agents invoke refresh_cache to trigger actions in Recon Fuzz Knowledge. 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.
This tool triggers an external operation — fetching and refreshing cached content from multiple remote sources. It is not a simple read (it has side effects on the cache state) nor purely destructive, but it does execute an active network/refresh operation. Misuse could trigger repeated external requests (rate-limited to 60s), cause cache invalidation issues, or place load on external services.
From the tool's definition Force refresh the documentation cache from all three sources
Attacks that exploit this kind of access
Force refresh the documentation cache from all three sources (getrecon.xyz, book.getrecon.xyz, getrecon.substack.com). Rate limited to once per 60 seconds. It is categorised as a Execute tool in the Recon Fuzz Knowledge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Recon Fuzz Knowledge MCP server in PolicyLayer and add a rule for refresh_cache: 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 Recon Fuzz Knowledge. Nothing to install.
refresh_cache 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 refresh_cache 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 refresh_cache. 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.
refresh_cache is provided by the Recon Fuzz Knowledge MCP server (recon-fuzz/recon-mcp-knowledge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →