Delete a user account (requires admin permissions)
AI agents call delete_user to permanently remove resources in BookStack MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
User account deletion is a destructive operation that cannot be easily undone. It removes identity records, potentially access permissions, and associated metadata from the system. While the blast radius is somewhat contained (affects one user account rather than bulk data), the irreversible nature and admin-level permissions required place this in the Destructive category.
From the tool's definition Tool name is 'delete_user' and description states 'Delete a user account'. The verb 'delete' combined with 'user account' indicates irreversible removal of user identity and associated data.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Delete a user account (requires admin permissions). It is categorised as a Destructive tool in the BookStack MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the BookStack MCP Server MCP server in PolicyLayer and add a rule for delete_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 BookStack MCP Server. Nothing to install.
delete_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 delete_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 delete_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.
delete_user is provided by the BookStack MCP Server MCP server (lautarobarba/bookstack_mcp_server). 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 →