[CUSTOM] Calls the Marketo REST API directly (not Adobe's native MCP).
AI agents invoke custom_send_sample_email to trigger actions in Marketo MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes an external operation (sending a sample email) by calling the Marketo REST API directly. Sending emails is an external side effect that cannot be trivially undone, and misuse could result in unintended emails being sent to leads or contacts.
From the tool's definition 'custom_send_sample_email' and description 'Calls the Marketo REST API directly' — triggers an external email-sending operation via the Marketo REST API
Attacks that exploit this kind of access
[CUSTOM] Calls the Marketo REST API directly (not Adobe's native MCP). It is categorised as a Execute tool in the Marketo MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Marketo MCP Server MCP server in PolicyLayer and add a rule for custom_send_sample_email: 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_send_sample_email is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the custom_send_sample_email 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_send_sample_email. 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_send_sample_email 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 →