custom_remove_user_roles
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.
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.
Attacks that exploit this kind of access
custom_remove_user_roles. 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_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.
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.
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.
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.
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.
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 →