Clear all cached data. Useful for debugging or forcing fresh data.
AI agents call clear_cache to permanently remove resources in Basecamp MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Clearing all cached data is an irreversible action (the cache cannot be restored once wiped). While the underlying Basecamp data is unaffected, loss of the cache could cause performance degradation and loss of any cached state. This qualifies as Destructive given its irreversibility, though the blast radius is limited since source data remains intact, placing severity at medium.
From the tool's definition 'Clear all cached data' — irreversibly removes all cached data, forcing fresh fetches
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Clear all cached data. Useful for debugging or forcing fresh data. It is categorised as a Destructive tool in the Basecamp MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Basecamp MCP Server 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 Basecamp MCP Server. 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 Basecamp MCP Server MCP server (kbhalerao/basecamp-mcp). 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 →