custom_sync_leads
AI agents use custom_sync_leads 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.
The name 'custom_sync_leads' implies a sync operation on leads, which in Marketo's REST API context typically means upsert (create or update) operations on lead records. This falls under Write as it modifies CRM/marketing data. Without a description, confidence is reduced, but the Marketo API's syncLeads endpoint is well-known for creating/updating leads.
From the tool's definition Tool name 'custom_sync_leads' suggests synchronizing lead data; 'sync' typically implies creating or updating records. Description is empty, lowering confidence.
Attacks that exploit this kind of access
custom_sync_leads. 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 custom_sync_leads: 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_sync_leads 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 custom_sync_leads 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_sync_leads. 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_sync_leads 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 →