New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

custom_update_lead_field

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

SERVERMarketo MCP Server SOURCEtyron-pretorius/marketo-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/tyron-pretorius-marketo-mcp/custom-update-lead-field.md

What custom_update_lead_field does on Marketo MCP Server

AI agents use custom_update_lead_field 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 custom_update_lead_field is rated Medium

This tool modifies lead data fields, making it a Write category operation. Severity is high because lead records are critical business assets in marketing automation; a misused update could corrupt contact information, segmentation data, or campaign eligibility across potentially thousands of records.

From the tool's definition Tool name 'custom_update_lead_field' explicitly performs field updates on leads. Description states it 'Calls the Marketo REST API directly' for lead field modification.

Questions about custom_update_lead_field

What does the custom_update_lead_field tool do? +

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

How do I enforce a policy on custom_update_lead_field? +

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

custom_update_lead_field is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit custom_update_lead_field? +

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

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Marketo MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.