New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

remove_user

A destructive tool on the Ludus Fast MCP server.

SERVERLudus FastMCP SOURCEtjnull/ludus-fastmcp
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/tjnull-ludus-fastmcp/remove-user.md

What remove_user does on Ludus FastMCP

AI agents call remove_user to permanently remove resources in Ludus FastMCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why remove_user is rated Critical

User account removal is a destructive operation that cannot be undone—deleted user profiles, permissions, and access cannot be automatically restored. While the description is empty (lowering confidence slightly), the tool name 'remove_user' on a Windows management server unambiguously indicates account deletion.

From the tool's definition Tool name 'remove_user' combined with Windows Operations server context that provides 'comprehensive Windows system management' including user operations. The tool removes a user account, which is irreversible account deletion.

Questions about remove_user

What does the remove_user tool do? +

remove_user is a destructive tool on the Ludus Fast MCP server. It is categorised as a Destructive tool in the Ludus FastMCP 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 remove_user? +

Register the Ludus Fast 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 Ludus FastMCP. Nothing to install.

What risk level is remove_user? +

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

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.

How do I block remove_user completely? +

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.

What MCP server provides remove_user? +

remove_user is provided by the Ludus Fast MCP server (tjnull/ludus-fastmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Ludus Fast, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Ludus Fast's. Pull the full record:

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.