mikrotik_remove_user

Removes a user from MikroTik device

SERVERMikroTik Cursor MCP SOURCEkevinpez/mikrotik-cursor-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/kevinpez-mikrotik-cursor-mcp/mikrotik-remove-user.md

WHAT IT DOES

What mikrotik_remove_user does on MikroTik Cursor MCP

AI agents call mikrotik_remove_user to permanently remove resources in MikroTik Cursor MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why mikrotik_remove_user is rated Critical

Removing a user account is an irreversible destructive action that cannot be undone without manual recreating the account and reassigning permissions. This is more severe than Write (which is reversible) and falls squarely into Destructive category. The blast radius is high because unauthorized user removal could lock administrators out of router management or disrupt legitimate access.

From the tool's definition Tool name includes 'remove' and description states 'Removes a user from MikroTik device' — this irreversibly deletes user account access credentials and configurations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mikrotik_remove_user safely

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

mikrotik_remove_user Hidden

mikrotik_remove_user 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": [
    "mikrotik_remove_user"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect MikroTik Cursor MCP, apply this rule, and every mikrotik_remove_user call is checked against it from then on.

FAQ

Questions about mikrotik_remove_user

What does the mikrotik_remove_user tool do? +

Removes a user from MikroTik device. It is categorised as a Destructive tool in the MikroTik Cursor 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 mikrotik_remove_user? +

Register the MikroTik Cursor MCP server in PolicyLayer and add a rule for mikrotik_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 MikroTik Cursor MCP. Nothing to install.

What risk level is mikrotik_remove_user? +

mikrotik_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 mikrotik_remove_user? +

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

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

mikrotik_remove_user is provided by the MikroTik Cursor MCP server (kevinpez/mikrotik-cursor-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on MikroTik Cursor, and thousands of servers like it.

This server

All 452 MikroTik Cursor tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →delete_mysql_user on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →