This record as markdown: /tools/atharva-joshi77-cdp-mcp/cdp-get-connector.md
What cdp_get_connector does on CDP MCP Server
AI agents call cdp_get_connector to retrieve information from CDP MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why cdp_get_connector is rated Low
This tool retrieves connector configuration information by ID. It performs a simple query/fetch operation with no capability to modify, delete, or execute external actions. The 'get' operation and read-only nature classify this as a Read category tool.
From the tool's definition Tool name 'cdp_get_connector' with description 'Get a specific connector by ID' indicates retrieval of existing connector metadata without modification or side effects.
Attacks that exploit this kind of access
The rule that runs cdp_get_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_get_connector, this is the rule to start with:
cdp_get_connector is read-only, so it stays allowed. 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_get_connector call is checked against it from then on.
Questions about cdp_get_connector
Get a specific connector by ID. It is categorised as a Read tool in the CDP MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CDP MCP Server MCP server in PolicyLayer and add a rule for cdp_get_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_get_connector is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the cdp_get_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_get_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_get_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