[CUSTOM] Calls the Marketo REST API directly (not Adobe's native MCP).
AI agents call custom_delete_companies 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.
The tool name explicitly references deletion of company records. Deletion is irreversible and removes data permanently from the Marketo database. This is more severe than Write (which is reversible) or Execute (which may have conditional effects).
From the tool's definition Tool name 'custom_delete_companies' contains 'delete', which indicates irreversible removal of data. The description states it 'Calls the Marketo REST API directly', confirming it performs API operations.
Attacks that exploit this kind of access
[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.
Register the Marketo MCP Server MCP server in PolicyLayer and add a rule for custom_delete_companies: 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.
custom_delete_companies 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 custom_delete_companies 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 custom_delete_companies. 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.
custom_delete_companies 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 →