custom_delete_custom_object_type_fields
[CUSTOM] Calls the Marketo REST API directly (not Adobe's native MCP).
This record as markdown: /tools/tyron-pretorius-marketo-mcp/custom-delete-custom-object-type-fields.md
What custom_delete_custom_object_type_fields does on Marketo MCP Server
AI agents call custom_delete_custom_object_type_fields to permanently remove resources in Marketo MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why custom_delete_custom_object_type_fields is rated Critical
The 'delete' action is inherently destructive and irreversible. Deleting custom object type fields in a marketing automation system like Marketo will permanently remove those field definitions and associated data, affecting campaigns, leads, and program configurations that depend on those fields. This cannot be easily undone and has high blast radius if triggered incorrectly by an AI agent.
From the tool's definition Tool name contains 'delete' and 'fields', indicating irreversible removal of custom object type field definitions. Description states it 'Calls the Marketo REST API directly,' which is a pass-through for API operations that modify Marketo data structures.
Attacks that exploit this kind of access
The rule that runs custom_delete_custom_object_type_fields 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_delete_custom_object_type_fields, this is the rule to start with:
custom_delete_custom_object_type_fields is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Marketo MCP Server, apply this rule, and every custom_delete_custom_object_type_fields call is checked against it from then on.
Questions about custom_delete_custom_object_type_fields
[CUSTOM] Calls the Marketo REST API directly (not Adobe's native MCP). It is categorised as a Destructive tool in the Marketo MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Marketo MCP Server MCP server in PolicyLayer and add a rule for custom_delete_custom_object_type_fields: 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.
custom_delete_custom_object_type_fields is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the custom_delete_custom_object_type_fields 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.
Set action: deny in the PolicyLayer policy for custom_delete_custom_object_type_fields. 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.
custom_delete_custom_object_type_fields 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.
Across the catalogue