user_permissions_delete

[DELETE] Revoke a user\

SERVERSamarth Gtm Mcp SOURCEsamarth-gtm-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/io-github-samarthanalytics-sj-samarth-gtm-mcp/user-permissions-delete.md

WHAT IT DOES

What user_permissions_delete does on Samarth Gtm Mcp

AI agents call user_permissions_delete to permanently remove resources in Samarth Gtm Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why user_permissions_delete is rated Critical

This tool permanently removes user permissions/access, which cannot be automatically undone and represents an irreversible destructive action. Although the server is described as 'read-only by default, gated writes, audits', this tool explicitly performs a destructive operation (DELETE).

From the tool's definition Tool name contains '[DELETE]' and description states 'Revoke a user', indicating irreversible removal of access permissions.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs user_permissions_delete safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Samarth Gtm Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For user_permissions_delete, this is the rule to start with:

user_permissions_delete Hidden

user_permissions_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "user_permissions_delete"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Samarth Gtm Mcp, apply this rule, and every user_permissions_delete call is checked against it from then on.

FAQ

Questions about user_permissions_delete

What does the user_permissions_delete tool do? +

[DELETE] Revoke a user\. It is categorised as a Destructive tool in the Samarth Gtm Mcp 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 user_permissions_delete? +

Register the Samarth Gtm MCP server in PolicyLayer and add a rule for user_permissions_delete: 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 Samarth Gtm Mcp. Nothing to install.

What risk level is user_permissions_delete? +

user_permissions_delete 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 user_permissions_delete? +

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

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

user_permissions_delete is provided by the Samarth Gtm MCP server (samarth-gtm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Samarth Gtm, and thousands of servers like it.

This server

All 236 Samarth Gtm tools → Critical-risk tools on this server →

Across the catalogue

delete_mysql_user on cPanel MCP Server →sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →