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

custom_delete_static_list

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

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

This record as markdown: /tools/tyron-pretorius-marketo-mcp/custom-delete-static-list.md

What custom_delete_static_list does on Marketo MCP Server

AI agents call custom_delete_static_list 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_static_list is rated Critical

Deleting a static list permanently removes lead data and cannot be undone. This is a destructive operation with high blast radius if misused by an AI agent—it could eliminate critical contact databases, segments, or audiences. The custom API wrapper and lack of detailed operation description slightly lower confidence from critical to high, but the destructive nature of deletion is clear.

From the tool's definition Tool name contains 'delete' and 'static_list'; description indicates it calls Marketo REST API directly for custom operations. The 'delete' operation on a static list (a collection of leads/contacts in Marketo) is irreversible data removal.

Questions about custom_delete_static_list

What does the custom_delete_static_list 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_static_list? +

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

custom_delete_static_list 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_static_list? +

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

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

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