custom_delete_user_invite

[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_user_invite does on Marketo MCP Server

AI agents call custom_delete_user_invite 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_user_invite needs a policy

The 'delete' operation in the tool name indicates irreversible removal of user invitations. Combined with the custom implementation and direct API access (bypassing Adobe's native MCP controls), this represents a Destructive category risk. Severity is high due to the irreversible nature and potential impact on user access management, though not critical without evidence of broader system compromise.

From the tool's definition Tool name contains 'delete' and 'user_invite'; description indicates direct Marketo REST API calls without Adobe's native MCP safeguards. The 'CUSTOM' prefix and circumvention of native MCP suggest potential for unvetted destructive operations.

Questions about custom_delete_user_invite

What does the custom_delete_user_invite 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_user_invite? +

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

custom_delete_user_invite 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_user_invite? +

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

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

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