cdp_update_a360_rule
Update an existing A360 rule. Pass updated fields as a JSON string.
This record as markdown: /tools/atharva-joshi77-cdp-mcp/cdp-update-a360-rule.md
What cdp_update_a360_rule does on CDP MCP Server
AI agents use cdp_update_a360_rule 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_update_a360_rule is rated Medium
This tool modifies existing configuration data (A360 rules) in a CDP system. While reversible via subsequent updates, it affects marketing automation rules that could impact customer targeting, campaign execution, and data segmentation. The high severity reflects the potential business impact if an AI agent misuses this to update rules incorrectly, affecting active marketing operations and customer communications.
From the tool's definition Tool name includes 'update' and description states 'Update an existing A360 rule', indicating modification of existing data. A360 rules are a core component of CDP marketing automation and targeting logic.
Attacks that exploit this kind of access
The rule that runs cdp_update_a360_rule 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_update_a360_rule, this is the rule to start with:
cdp_update_a360_rule 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_update_a360_rule call is checked against it from then on.
Questions about cdp_update_a360_rule
Update an existing A360 rule. Pass updated fields 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_update_a360_rule: 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_update_a360_rule 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_update_a360_rule 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_update_a360_rule. 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_update_a360_rule 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