cdp_create_output_connector
Create a new output connector. Pass configuration as a JSON string.
This record as markdown: /tools/atharva-joshi77-cdp-mcp/cdp-create-output-connector.md
What cdp_create_output_connector does on CDP MCP Server
AI agents use cdp_create_output_connector to create or update resources in CDP MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CDP MCP Server environment.
Why cdp_create_output_connector is rated Medium
This tool creates a new resource (output connector) that reversibly modifies the CDP configuration. While creation is reversible (connectors can typically be deleted or disabled), the blast radius is high because a misconfigured or malicious output connector could redirect sensitive customer data to unauthorized external systems, exposing PII and customer information.
From the tool's definition Tool name 'cdp_create_output_connector' and description 'Create a new output connector' indicate data creation. Output connectors are integration points that send customer data to external systems (e.g., email providers, advertising platforms, CRM systems).
Attacks that exploit this kind of access
The rule that runs cdp_create_output_connector 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_create_output_connector, this is the rule to start with:
cdp_create_output_connector stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect CDP MCP Server, apply this rule, and every cdp_create_output_connector call is checked against it from then on.
Questions about cdp_create_output_connector
Create a new output connector. Pass configuration as a JSON string. It is categorised as a Write tool in the CDP MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CDP MCP Server MCP server in PolicyLayer and add a rule for cdp_create_output_connector: 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_create_output_connector is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the cdp_create_output_connector 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_create_output_connector. 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_create_output_connector 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.
This server
Across the catalogue