describe_leads

Get lead field metadata and schema information from Marketo.

SERVERMarketo MCP Server SOURCEtyron-pretorius/marketo-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/tyron-pretorius-marketo-mcp/describe-leads.md

WHAT IT DOES

What describe_leads does on Marketo MCP Server

AI agents call describe_leads 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.

RISK

Why describe_leads is rated Low

The describe_leads tool queries and returns schema metadata about leads in Marketo. This is a read-only operation that retrieves information without creating, modifying, deleting, or executing any changes. The blast radius of misuse is minimal since it only exposes structural data definitions rather than actual lead records or sensitive operational data. Low severity is appropriate for metadata retrieval operations.

From the tool's definition Tool retrieves 'lead field metadata and schema information' from Marketo—a data retrieval operation with no modification capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs describe_leads 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 describe_leads, this is the rule to start with:

describe_leads Allowed

describe_leads is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "describe_leads": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Marketo MCP Server, apply this rule, and every describe_leads call is checked against it from then on.

FAQ

Questions about describe_leads

What does the describe_leads tool do? +

Get lead field metadata and schema information from Marketo. It is categorised as a Read tool in the Marketo MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on describe_leads? +

Register the Marketo MCP Server MCP server in PolicyLayer and add a rule for describe_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 describe_leads? +

describe_leads is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit describe_leads? +

Yes. Add a rate_limit block to the describe_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 describe_leads completely? +

Set action: deny in the PolicyLayer policy for describe_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 describe_leads? +

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

KEEP EXPLORING

More on Marketo MCP Server, and thousands of servers like it.

This server

All 298 Marketo MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →