This record as markdown: /tools/atharva-joshi77-cdp-mcp/cdp-login.md
What cdp_login does on CDP MCP Server
AI agents invoke cdp_login to trigger actions in CDP MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why cdp_login is rated High
This tool performs a POST to an authentication endpoint with an explicit action parameter, meaning it executes an external operation (creating a session or issuing an auth token) rather than simply reading data. It is not purely a read, nor is it destructive or financial, but it does trigger state changes on the server (session/token creation), placing it in Execute.
From the tool's definition POST /authentication?action=login — triggers an external authentication operation with side effects (session creation, token issuance)
Attacks that exploit this kind of access
The rule that runs cdp_login 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_login, this is the rule to start with:
cdp_login stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_login call is checked against it from then on.
Questions about cdp_login
POST /authentication?action=login. It is categorised as a Execute tool in the CDP MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the CDP MCP Server MCP server in PolicyLayer and add a rule for cdp_login: 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_login is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the cdp_login 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_login. 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_login 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.
Across the catalogue