Removes a simple queue
AI agents call mikrotik_remove_simple_queue 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.
This tool performs an irreversible deletion operation on MikroTik router configuration (queue removal). While not data deletion per se, it permanently removes active traffic management settings. The blast radius is significant—removing a queue on a production network could disrupt traffic shaping policies and service quality without easy recovery.
From the tool's definition The tool name explicitly states 'remove' and the description confirms it 'Removes a simple queue'. Removal of network queue configuration is an irreversible deletion action that cannot be undone without reconfiguring.
Attacks that exploit this kind of access
Removes a simple queue. 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.
Register the MikroTik Cursor MCP server in PolicyLayer and add a rule for mikrotik_remove_simple_queue: 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.
mikrotik_remove_simple_queue 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 mikrotik_remove_simple_queue 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_remove_simple_queue. 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_remove_simple_queue 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.
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 →