custom_push_leads · Marketo MCP Server MCP: Risk & Policy

WHAT IT DOES

What custom_push_leads does on Marketo MCP Server

AI agents invoke custom_push_leads to trigger actions in Marketo MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why custom_push_leads needs a policy

Pushing leads into Marketo via a direct REST API call is an external operation that creates or modifies lead records and can trigger associated smart campaigns, scoring rules, and workflows. The effects depend heavily on the arguments supplied, making this Execute (potentially Write at minimum). The custom/direct API nature and the ability to trigger downstream automation elevates severity to high.

From the tool's definition 'Calls the Marketo REST API directly' and 'push_leads' — triggers an external API operation that pushes lead data into Marketo, an action whose full effects depend on arguments

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

custom_push_leads Rate-limited

custom_push_leads stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "custom_push_leads": {
      "limits": [
        {
          "counter": "custom_push_leads_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Marketo MCP Server, so you can run agents against it safely.

FAQ

Questions about custom_push_leads

What does the custom_push_leads tool do? +

[CUSTOM] Calls the Marketo REST API directly (not Adobe's native MCP). It is categorised as a Execute tool in the Marketo MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on custom_push_leads? +

Register the Marketo MCP Server MCP server in PolicyLayer and add a rule for custom_push_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.

What risk level is custom_push_leads? +

custom_push_leads is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit custom_push_leads? +

Yes. Add a rate_limit block to the custom_push_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.

How do I block custom_push_leads completely? +

Set action: deny in the PolicyLayer policy for custom_push_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.

What MCP server provides custom_push_leads? +

custom_push_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.