Clear the RSS feed cache
AI agents call clear_cache to permanently remove resources in ContextForge MCP Gateway — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Clearing a cache is an irreversible deletion of stored data. While the data can be regenerated by re-fetching the RSS feeds, the cached state itself is permanently destroyed. This is a Destructive action with medium severity: the blast radius is limited to cache invalidation and potential temporary performance degradation or feed unavailability, but it does not affect primary source data.
From the tool's definition 'Clear the RSS feed cache' — clearing a cache irreversibly removes stored data (cached RSS feed content), requiring it to be re-fetched
Attacks that exploit this kind of access
Clear the RSS feed cache. It is categorised as a Destructive tool in the ContextForge MCP Gateway MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ContextForge MCP Gateway MCP server in PolicyLayer and add a rule for clear_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 ContextForge MCP Gateway. Nothing to install.
clear_cache is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the clear_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 clear_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.
clear_cache is provided by the ContextForge MCP Gateway MCP server (jrmatherly/mcp-context-forge). 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 →