cdp_delete_user

Delete a CDP user by ID

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-delete-user.md

WHAT IT DOES

What cdp_delete_user does on CDP MCP Server

AI agents call cdp_delete_user 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.

RISK

Why cdp_delete_user is rated Critical

This tool performs an irreversible deletion operation on user entities within the CDP system. Deletion of user accounts is a destructive action that cannot be reversed without manual intervention (account recreation, data restoration). The 'Destructive' category is most appropriate as it involves permanent removal of data.

From the tool's definition Tool name 'cdp_delete_user' combined with description 'Delete a CDP user by ID' explicitly indicates irreversible deletion of user data. The verb 'delete' and the action of removing a user account cannot be undone.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cdp_delete_user 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_delete_user, this is the rule to start with:

cdp_delete_user Hidden

cdp_delete_user is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "cdp_delete_user"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect CDP MCP Server, apply this rule, and every cdp_delete_user call is checked against it from then on.

FAQ

Questions about cdp_delete_user

What does the cdp_delete_user tool do? +

Delete a CDP user by ID. 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_delete_user? +

Register the CDP MCP Server MCP server in PolicyLayer and add a rule for cdp_delete_user: 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_delete_user? +

cdp_delete_user 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_delete_user? +

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

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

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

KEEP EXPLORING

More on CDP MCP Server, and thousands of servers like it.

This server

All 288 CDP MCP Server tools → Critical-risk tools on this server →

Across the catalogue

delete_mysql_user on cPanel MCP Server →sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →