custom_delete_opportunities

[CUSTOM] Calls the Marketo REST API directly (not Adobe's native MCP).

Server Marketo MCP Server tyron-pretorius/marketo-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What custom_delete_opportunities does on Marketo MCP Server

AI agents call custom_delete_opportunities 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.

Why custom_delete_opportunities needs a policy

The tool name unambiguously indicates deletion of opportunities, which are irreversible business-critical data in Marketo. Even though the description is minimal and marked '[CUSTOM]', the name itself is definitive—delete operations cannot be undone and represent permanent data loss. This poses high blast radius risk if an AI agent is misdirected or prompted maliciously to remove opportunity records.

From the tool's definition Tool name 'custom_delete_opportunities' explicitly uses 'delete'; description states it 'Calls the Marketo REST API directly'; Marketo opportunities are core business data (sales pipeline objects)

Questions about custom_delete_opportunities

What does the custom_delete_opportunities tool do? +

[CUSTOM] Calls the Marketo REST API directly (not Adobe's native MCP). 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.

How do I enforce a policy on custom_delete_opportunities? +

Register the Marketo MCP Server MCP server in PolicyLayer and add a rule for custom_delete_opportunities: 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.

What risk level is custom_delete_opportunities? +

custom_delete_opportunities is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit custom_delete_opportunities? +

Yes. Add a rate_limit block to the custom_delete_opportunities 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.

How do I block custom_delete_opportunities completely? +

Set action: deny in the PolicyLayer policy for custom_delete_opportunities. 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.

What MCP server provides custom_delete_opportunities? +

custom_delete_opportunities 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.