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

custom_delete_named_accounts

[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-named-accounts.md

What custom_delete_named_accounts does on Marketo MCP Server

AI agents call custom_delete_named_accounts 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_named_accounts is rated Critical

The tool performs deletion of named accounts in Marketo, which is an irreversible operation that cannot be undone. This fits the Destructive category definition (irreversibly deletes data).

From the tool's definition Tool name contains 'delete' and description indicates it 'Calls the Marketo REST API directly' for named accounts management. Named accounts are core CRM entities in Marketo; deletion is irreversible.

Questions about custom_delete_named_accounts

What does the custom_delete_named_accounts 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_named_accounts? +

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

custom_delete_named_accounts 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_named_accounts? +

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

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

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