Delete a smart campaign in Marketo.
AI agents call delete_smart_campaign to permanently remove resources in Marketo MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a smart campaign cannot be undone and removes configured marketing automation logic, potentially disrupting ongoing campaign execution and business processes. This warrants Destructive classification with high severity due to the permanent loss of marketing assets and potential operational impact.
From the tool's definition Tool name explicitly states 'delete' and description confirms 'Delete a smart campaign in Mark eto' — this is an irreversible removal operation.
Attacks that exploit this kind of access
Delete a smart campaign in Marketo. It is categorised as a Destructive tool in the Marketo MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Marketo MCP Server MCP server in PolicyLayer and add a rule for delete_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.
delete_smart_campaign is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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 →