cache_delete
Delete a value from the optional Redis companion cache
This record as markdown: /tools/1999azzar-project-guardian-mcp-server/cache-delete.md
What cache_delete does on Project Guardian MCP
AI agents call cache_delete to permanently remove resources in Project Guardian MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why cache_delete is rated Critical
This tool permanently removes cached data from Redis. While the data may be reconstructable from source systems in some scenarios, the deletion itself is irreversible and the tool's primary function is destructive. The high severity reflects that cache corruption or loss could disrupt workflow management and project context persistence in the broader system.
From the tool's definition Tool name: 'cache_delete'. Description explicitly states: 'Delete a value from the optional Redis companion cache'. The verb 'Delete' combined with 'from cache' indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs cache_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Project Guardian MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cache_delete, this is the rule to start with:
cache_delete 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 Project Guardian MCP, apply this rule, and every cache_delete call is checked against it from then on.
Questions about cache_delete
Delete a value from the optional Redis companion cache. It is categorised as a Destructive tool in the Project Guardian MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Project Guardian MCP server in PolicyLayer and add a rule for cache_delete: 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 Project Guardian MCP. Nothing to install.
cache_delete 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 cache_delete 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 cache_delete. 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.
cache_delete is provided by the Project Guardian MCP server (1999azzar/project-guardian-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Project Guardian, and thousands of servers like it.
Across the catalogue