Disables a user account
AI agents use mikrotik_disable_user to create or update resources in MikroTik MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MikroTik MCP environment.
This tool modifies user account state by disabling it. Disabling an account is reversible (it can be re-enabled later), so it falls under Write rather than Destructive. The severity is medium because disabling a user account on a network device could disrupt legitimate access, but the impact is localized to access control and the action is not irreversible.
From the tool's definition Tool name is 'mikrotik_disable_user' and description states it 'Disables a user account'. Disabling is a reversible modification (the account can be re-enabled), not a deletion.
Attacks that exploit this kind of access
Disables a user account. It is categorised as a Write tool in the MikroTik MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MikroTik MCP server in PolicyLayer and add a rule for mikrotik_disable_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 MCP. Nothing to install.
mikrotik_disable_user is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the mikrotik_disable_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 mikrotik_disable_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.
mikrotik_disable_user is provided by the MikroTik MCP server (tarcisiodier/mcp-mikrotik). 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 →