stateset_clear_cache

Clears cached data to force fresh API calls. Use after making changes that aren

SERVERStateset SOURCEstateset/stateset-mcp-server
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about stateset_clear_cache

What does the stateset_clear_cache tool do? +

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.

How do I enforce a policy on stateset_clear_cache? +

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.

What risk level is stateset_clear_cache? +

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.

Can I rate-limit stateset_clear_cache? +

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.

How do I block stateset_clear_cache completely? +

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.

What MCP server provides stateset_clear_cache? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Stateset's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.