marketo_create_or_update_lead
Bulk create or update leads (upsert). Accepts an array of lead records with standard and custom fields. Deduplicates by lookupField (default: email). Max 300 leads per call.
This record as markdown: /tools/alexleventer-marketo-mcp/marketo-create-or-update-lead.md
What marketo_create_or_update_lead does on Marketo MCP Server
AI agents use marketo_create_or_update_lead to create or update resources in Marketo MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Marketo MCP Server environment.
Why marketo_create_or_update_lead is rated Medium
This tool creates and modifies customer data (lead records) in a marketing automation system. While reversible (records can be updated again), bulk upsert operations have significant business impact—incorrect data could corrupt customer databases, trigger unintended marketing campaigns, or affect sales processes. The high volume capacity (300 leads) increases blast radius.
From the tool's definition Tool performs 'create or update leads' (upsert) operations with bulk capabilities (300 leads max per call). The description explicitly states it modifies lead records by creating new records or updating existing ones.
Attacks that exploit this kind of access
The rule that runs marketo_create_or_update_lead 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_create_or_update_lead, this is the rule to start with:
marketo_create_or_update_lead stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_create_or_update_lead call is checked against it from then on.
Questions about marketo_create_or_update_lead
Bulk create or update leads (upsert). Accepts an array of lead records with standard and custom fields. Deduplicates by lookupField (default: email). Max 300 leads per call. It is categorised as a Write tool in the Marketo MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Marketo MCP Server MCP server in PolicyLayer and add a rule for marketo_create_or_update_lead: 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_create_or_update_lead is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the marketo_create_or_update_lead 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_create_or_update_lead. 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_create_or_update_lead 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