marketo_get_lead_by_email
Look up a lead by email address using the Marketo leads filter API. Optionally specify which fields to return. Returns matching lead records.
This record as markdown: /tools/alexleventer-marketo-mcp/marketo-get-lead-by-email.md
What marketo_get_lead_by_email does on Marketo MCP Server
AI agents call marketo_get_lead_by_email 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_lead_by_email is rated Low
This tool retrieves lead information from Marketo by filtering on email address. It is a read-only query operation that returns data without creating, modifying, or deleting records. The ability to look up lead contact information poses minimal risk — it is informational retrieval only.
From the tool's definition Tool name contains 'get_lead_by_email' and description states 'Look up a lead by email address' and 'Returns matching lead records' — these are query/retrieval operations with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs marketo_get_lead_by_email 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_lead_by_email, this is the rule to start with:
marketo_get_lead_by_email 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_lead_by_email call is checked against it from then on.
Questions about marketo_get_lead_by_email
Look up a lead by email address using the Marketo leads filter API. Optionally specify which fields to return. Returns matching lead records. 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_lead_by_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.
marketo_get_lead_by_email 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_lead_by_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 marketo_get_lead_by_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.
marketo_get_lead_by_email 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