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

custom_remove_user_roles

A destructive tool on the Marketo MCP server.

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-remove-user-roles.md

What custom_remove_user_roles does on Marketo MCP Server

AI agents call custom_remove_user_roles 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_remove_user_roles is rated Critical

Removing user roles is a destructive action that cannot be easily undone without administrative intervention. It permanently revokes access and permissions, affecting system security and user workflows. While the description is empty (lowering confidence slightly), the name itself clearly indicates a destructive operation on access control.

From the tool's definition Tool name 'custom_remove_user_roles' indicates removal/deletion of role assignments. The verb 'remove' combined with 'user_roles' in a system management context implies irreversible deletion of access permissions.

Questions about custom_remove_user_roles

What does the custom_remove_user_roles tool do? +

custom_remove_user_roles is a destructive tool on the Marketo MCP Server MCP server. 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_remove_user_roles? +

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

custom_remove_user_roles 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_remove_user_roles? +

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

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

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