Remove (delete) a user by email. This action is irreversible. You must confirm with the user that they want to remove the user before actually calling this tool.
AI agents call remove-user to permanently remove resources in Dynamic MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes user accounts and cannot be undone. While not a financial transaction, the irreversible nature of user deletion and its potential impact on system access, data associations, and user management makes this a Destructive action.
From the tool's definition Tool description explicitly states 'Remove (delete) a user by email' and 'This action is irreversible.' The verb 'delete' and phrase 'irreversible' directly indicate permanent data removal.
Documented attack patterns abuse exactly the kind of access remove-user gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Dynamic MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for remove-user:
{
"version": "1",
"default": "deny",
"hide": [
"remove-user"
]
} remove-user disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove (delete) a user by email. This action is irreversible. You must confirm with the user that they want to remove the user before actually calling this tool. It is categorised as a Destructive tool in the Dynamic MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Dynamic MCP Server MCP server in PolicyLayer and add a rule for remove-user: 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 Dynamic MCP Server. Nothing to install.
remove-user 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 remove-user 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 remove-user. 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.
remove-user is provided by the Dynamic MCP Server MCP server (scitara-cto/dynamic-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Dynamic MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 Dynamic MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.