custom_describe_lead2

[CUSTOM] Calls the Marketo REST API directly (not Adobe's native MCP).

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/custom-describe-lead2.md

WHAT IT DOES

What custom_describe_lead2 does on Marketo MCP Server

AI agents call custom_describe_lead2 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 custom_describe_lead2 is rated Low

The name 'describe_lead2' strongly implies a metadata description/introspection operation (analogous to Salesforce's describeSObject), which is a read-only operation. However, the description is largely uninformative ('Calls the Marketo REST API directly') and does not confirm this, meaning the tool could potentially perform write or execute operations depending on what API it actually calls.

From the tool's definition 'custom_describe_lead2' and 'Calls the Marketo REST API directly' — the name suggests a 'describe' operation (metadata retrieval about a lead object), which is typically a read/introspection call

Attacks that exploit this kind of access

RECOMMENDED RULE

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

custom_describe_lead2 Allowed

custom_describe_lead2 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": {
    "custom_describe_lead2": {}
  }
}

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 custom_describe_lead2 call is checked against it from then on.

FAQ

Questions about custom_describe_lead2

What does the custom_describe_lead2 tool do? +

[CUSTOM] Calls the Marketo REST API directly (not Adobe's native MCP). 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 custom_describe_lead2? +

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

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

Can I rate-limit custom_describe_lead2? +

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

Set action: deny in the PolicyLayer policy for custom_describe_lead2. 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_describe_lead2? +

custom_describe_lead2 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 →