cdp_cache_delete_by_key
Delete a cache entry by explicit key. Returns 204 on success.
This record as markdown: /tools/atharva-joshi77-cdp-mcp/cdp-cache-delete-by-key.md
What cdp_cache_delete_by_key does on CDP MCP Server
AI agents call cdp_cache_delete_by_key to permanently remove resources in CDP MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why cdp_cache_delete_by_key is rated Critical
This tool permanently removes data (cache entries) by key, which cannot be undone. This matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' The high severity reflects that an agent with poor input validation could delete critical cache entries that other operations depend on, potentially breaking workflows or data pipelines across the CDP system.
From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete a cache entry by explicit key.' The operation is irreversible—once deleted, the cache entry cannot be recovered without external restoration.
Attacks that exploit this kind of access
The rule that runs cdp_cache_delete_by_key safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CDP MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cdp_cache_delete_by_key, this is the rule to start with:
cdp_cache_delete_by_key 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 CDP MCP Server, apply this rule, and every cdp_cache_delete_by_key call is checked against it from then on.
Questions about cdp_cache_delete_by_key
Delete a cache entry by explicit key. Returns 204 on success. It is categorised as a Destructive tool in the CDP MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the CDP MCP Server MCP server in PolicyLayer and add a rule for cdp_cache_delete_by_key: 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 CDP MCP Server. Nothing to install.
cdp_cache_delete_by_key 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 cdp_cache_delete_by_key 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 cdp_cache_delete_by_key. 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.
cdp_cache_delete_by_key is provided by the CDP MCP Server MCP server (atharva-joshi77/cdp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CDP MCP Server, and thousands of servers like it.
Across the catalogue