custom_delete_custom_object_type_fields

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

Server Marketo MCP Server tyron-pretorius/marketo-mcp
Category Destructive
Risk class Critical
Parameters 00 required

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 needs a policy

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.

Questions about custom_delete_custom_object_type_fields

What does the custom_delete_custom_object_type_fields tool do? +

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

How do I enforce a policy on custom_delete_custom_object_type_fields? +

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.

What risk level is custom_delete_custom_object_type_fields? +

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.

Can I rate-limit custom_delete_custom_object_type_fields? +

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.

How do I block custom_delete_custom_object_type_fields completely? +

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.

What MCP server provides custom_delete_custom_object_type_fields? +

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.

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