remove_site_user
Remove an admin user from your property.. Destructive - requires confirm: true in safe mode.
This record as markdown: /tools/com-zype-mcp-server/remove-site-user.md
What remove_site_user does on Zype Com
AI agents call remove_site_user to permanently remove resources in Zype Com, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | id (required) |
body | object | — | Request body fields |
confirm | boolean | — | Set true to confirm (required in safe mode) |
Parameters from the server's own tool schema.
Why remove_site_user is rated Critical
An AI agent that decides to call remove_site_user doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Zype Com is gone. There is no undo for destructive operations.
Risk signalsAccepts raw HTML/template content (body) · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs remove_site_user safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Zype Com, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_site_user, this is the rule to start with:
remove_site_user is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Zype Com, apply this rule, and every remove_site_user call is checked against it from then on.
Questions about remove_site_user
Remove an admin user from your property.. Destructive - requires confirm: true in safe mode. It is categorised as a Destructive tool in the Zype Com MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
remove_site_user accepts 3 parameters: id, body, confirm. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Zype Com MCP server in PolicyLayer and add a rule for remove_site_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 Zype Com. Nothing to install.
remove_site_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_site_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_site_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_site_user is provided by the Zype Com MCP server (zype/zype-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Zype Com, and thousands of servers like it.
Across the catalogue