stateset_clear_cache
Clears cached data to force fresh API calls. Use after making changes that aren
This record as markdown: /tools/stateset-mcp-server/stateset-clear-cache.md
What stateset_clear_cache does on Stateset
AI agents call stateset_clear_cache to permanently remove resources in Stateset, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why stateset_clear_cache is rated Critical
Clearing a cache is an irreversible action on the cached data (the cache cannot be 'uncleared'). While the underlying source data is not deleted, the cached entries are permanently removed. Severity is medium because the blast radius is limited to performance degradation and potential temporary unavailability of fast lookups, rather than loss of source data.
From the tool's definition 'Clears cached data' — permanently removes cached entries, forcing re-fetch; description is truncated ('that aren') suggesting more context is missing
Attacks that exploit this kind of access
The rule that runs stateset_clear_cache safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stateset, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stateset_clear_cache, this is the rule to start with:
stateset_clear_cache is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Stateset, apply this rule, and every stateset_clear_cache call is checked against it from then on.
Questions about stateset_clear_cache
Clears cached data to force fresh API calls. Use after making changes that aren. It is categorised as a Destructive tool in the Stateset MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Stateset MCP server in PolicyLayer and add a rule for stateset_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 Stateset. Nothing to install.
stateset_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 stateset_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 stateset_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.
stateset_clear_cache is provided by the Stateset MCP server (stateset/stateset-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stateset, and thousands of servers like it.
Across the catalogue