custom_update_form_submit_button

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

Server Marketo MCP Server tyron-pretorius/marketo-mcp
Category Write
Risk class Medium
Parameters 00 required

What custom_update_form_submit_button does on Marketo MCP Server

AI agents use custom_update_form_submit_button 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_form_submit_button needs a policy

This tool modifies form submit button configuration in Marketo, which is a reversible write operation. It does not delete data (Destructive), execute arbitrary code (Execute), or move money (Financial). However, severity is high because modifying form UI could affect lead capture and customer experience across campaigns if misconfigured by an AI agent.

From the tool's definition Tool name 'custom_update_form_submit_button' indicates modification of form UI elements. Description states it 'Calls the Marketo REST API directly', enabling updates to marketing asset configuration.

Questions about custom_update_form_submit_button

What does the custom_update_form_submit_button 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_form_submit_button? +

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

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

Can I rate-limit custom_update_form_submit_button? +

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

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

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.