cdp_cache_delete_by_id

Delete a cache entry by ID. Returns 204 on success.

SERVERCDP MCP Server SOURCEatharva-joshi77/cdp-mcp
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/atharva-joshi77-cdp-mcp/cdp-cache-delete-by-id.md

What cdp_cache_delete_by_id does on CDP MCP Server

AI agents call cdp_cache_delete_by_id 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_id is rated Critical

This tool irreversibly removes cached data by ID. Deletion operations cannot be undone and represent a destructive action with potential blast radius depending on what cached data is critical to CDP operations. While cache deletion may be less severe than deleting primary data, it is still a destructive operation that warrants the Destructive category over Write, as the action cannot be reversed.

From the tool's definition Tool name contains 'delete' and description states 'Delete a cache entry by ID. Returns 204 on success.' The 204 response code confirms successful deletion.

Questions about cdp_cache_delete_by_id

What does the cdp_cache_delete_by_id tool do? +

Delete a cache entry by ID. 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.

How do I enforce a policy on cdp_cache_delete_by_id? +

Register the CDP MCP Server MCP server in PolicyLayer and add a rule for cdp_cache_delete_by_id: 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.

What risk level is cdp_cache_delete_by_id? +

cdp_cache_delete_by_id 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 cdp_cache_delete_by_id? +

Yes. Add a rate_limit block to the cdp_cache_delete_by_id 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 cdp_cache_delete_by_id completely? +

Set action: deny in the PolicyLayer policy for cdp_cache_delete_by_id. 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 cdp_cache_delete_by_id? +

cdp_cache_delete_by_id 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.

// 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 CDP MCP Server'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.