Clear cached timesheet data. Useful when you want to force fresh data fetch for all future requests.
AI agents call clear_cache to permanently remove resources in Activity Collector MCP — 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 underlying source data is not lost, the cached timesheet data is permanently removed and cannot be undone. This warrants the Destructive category. Severity is medium because the impact is limited to cached data (not source data), but misuse could cause performance degradation and loss of aggregated/processed cache state.
From the tool's definition 'Clear cached timesheet data' — irreversibly removes cached data, forcing future fetches to retrieve fresh data; the cache cannot be restored once cleared.
Attacks that exploit this kind of access
Clear cached timesheet data. Useful when you want to force fresh data fetch for all future requests. It is categorised as a Destructive tool in the Activity Collector MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Activity Collector 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 Activity Collector MCP. 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 Activity Collector MCP server (srdmathur/activity-collector-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
clear_cache is one line of Activity Collector's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →