marketo_get_emails
List email assets in Marketo. Filter by approval status (approved/draft) and paginate with maxReturn/offset. Returns email metadata including subject line, from address, and template ID.
This record as markdown: /tools/alexleventer-marketo-mcp/marketo-get-emails.md
What marketo_get_emails does on Marketo MCP Server
AI agents call marketo_get_emails to retrieve information from Marketo MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why marketo_get_emails is rated Low
This tool retrieves and queries email asset metadata (subject line, from address, template ID) with filtering options. It has no side effects, creates no data, modifies nothing, and executes no operations. It is a straightforward read/list operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool description states 'List email assets in Marketo' and 'Returns email metadata' — purely informational retrieval with filtering and pagination parameters. No mutations, deletions, or external triggers mentioned.
Attacks that exploit this kind of access
The rule that runs marketo_get_emails safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Marketo MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For marketo_get_emails, this is the rule to start with:
marketo_get_emails is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Marketo MCP Server, apply this rule, and every marketo_get_emails call is checked against it from then on.
Questions about marketo_get_emails
List email assets in Marketo. Filter by approval status (approved/draft) and paginate with maxReturn/offset. Returns email metadata including subject line, from address, and template ID. 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 marketo_get_emails: 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.
marketo_get_emails 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 marketo_get_emails 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 marketo_get_emails. 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.
marketo_get_emails is provided by the Marketo MCP Server MCP server (alexleventer/marketo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Marketo MCP Server, and thousands of servers like it.
This server
Across the catalogue