cdp_delete_output_connector_def

Delete an output connector definition

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-output-connector-def.md

What cdp_delete_output_connector_def does on CDP MCP Server

AI agents call cdp_delete_output_connector_def 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_delete_output_connector_def is rated Critical

This tool irreversibly removes a connector definition from the CDP system. Deletion cannot be undone without manual restoration or API recreation. While not directly financial, the loss of connector configurations could disrupt data pipelines and campaigns, affecting multiple downstream systems. This makes it Destructive rather than Write (which implies reversible modification).

From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete an output connector definition'. Output connector definitions are configuration objects that manage data flow; deletion is irreversible.

Questions about cdp_delete_output_connector_def

What does the cdp_delete_output_connector_def tool do? +

Delete an output connector definition. 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_output_connector_def? +

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

cdp_delete_output_connector_def 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_output_connector_def? +

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

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

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