cdp_get_mailer_identifier_by_campaign_dispatch
A read tool on the CDP MCP server.
This record as markdown: /tools/atharva-joshi77-cdp-mcp/cdp-get-mailer-identifier-by-campaign-dispatch.md
What cdp_get_mailer_identifier_by_campaign_dispatch does on CDP MCP Server
AI agents call cdp_get_mailer_identifier_by_campaign_dispatch 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_mailer_identifier_by_campaign_dispatch is rated Low
The 'get' prefix and naming pattern (identifier retrieval) indicate this is a read operation that queries data about campaign dispatches without modifying, executing, or deleting anything. The empty description and lack of explicit destructive/execute keywords lower confidence slightly, but the strong naming convention and context of sibling read operations support the Read classification.
From the tool's definition Tool name contains 'get', indicating retrieval operation. Sibling tools show pattern of read operations (get_by_id, get_by_key, get_by_group). Tool retrieves mailer identifier information associated with a campaign dispatch.
Attacks that exploit this kind of access
The rule that runs cdp_get_mailer_identifier_by_campaign_dispatch 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_mailer_identifier_by_campaign_dispatch, this is the rule to start with:
cdp_get_mailer_identifier_by_campaign_dispatch 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_mailer_identifier_by_campaign_dispatch call is checked against it from then on.
Questions about cdp_get_mailer_identifier_by_campaign_dispatch
cdp_get_mailer_identifier_by_campaign_dispatch is a read tool on the CDP MCP Server MCP server. 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_mailer_identifier_by_campaign_dispatch: 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_mailer_identifier_by_campaign_dispatch 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_mailer_identifier_by_campaign_dispatch 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_mailer_identifier_by_campaign_dispatch. 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_mailer_identifier_by_campaign_dispatch 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