Get the content sections of an email asset from Marketo.
AI agents call get_email_content to retrieve information from Marketo MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves email content data from Marketo without creating, modifying, deleting, or executing any operations. It is a straightforward data retrieval (Read) operation. The blast radius is minimal—an AI agent retrieving email content poses no risk of data loss, unauthorized actions, or financial impact.
From the tool's definition Tool name is 'get_email_content' and description states 'Get the content sections of an email asset from Marketo.' The verb 'get' and explicit retrieval language indicate a read-only operation with no modification or side effects.
Attacks that exploit this kind of access
Get the content sections of an email asset from Marketo. It is categorised as a Read tool in the Marketo MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Marketo MCP Server MCP server in PolicyLayer and add a rule for get_email_content: 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.
get_email_content is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_email_content 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 get_email_content. 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.
get_email_content 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 →