Update an existing smart campaign in Marketo.
AI agents use update_smart_campaign to create or update resources in Marketo MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Marketo MCP Server environment.
This tool modifies existing smart campaign configurations reversibly. While not destructive (no deletion), updating a smart campaign is a Write operation that can affect marketing automation logic, targeting rules, and campaign flow—potentially impacting lead scoring, email delivery, and customer communications at scale.
From the tool's definition Tool name 'update_smart_campaign' and description 'Update an existing smart campaign in Marketo' indicate modification of existing marketing automation assets.
Attacks that exploit this kind of access
Update an existing smart campaign in Marketo. It is categorised as a Write tool in the Marketo MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Marketo MCP Server MCP server in PolicyLayer and add a rule for update_smart_campaign: 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 Marketo MCP Server. Nothing to install.
update_smart_campaign 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 update_smart_campaign 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 update_smart_campaign. 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.
update_smart_campaign is provided by the Marketo MCP Server MCP server (tyron-pretorius/marketo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →