mikrotik_remove_queue_tree
Removes a queue tree entry
This record as markdown: /tools/kevinpez-mikrotik-cursor-mcp/mikrotik-remove-queue-tree.md
What mikrotik_remove_queue_tree does on MikroTik Cursor MCP
AI agents call mikrotik_remove_queue_tree 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.
Why mikrotik_remove_queue_tree is rated Critical
Removing queue tree entries is a destructive action that modifies critical router traffic management configuration. While not as severe as deleting all routes or interfaces, it irreversibly removes QoS settings that could disrupt network traffic prioritization. The blast radius includes potential network degradation or service interruption if the wrong queue tree is removed, justifying 'high' severity.
From the tool's definition Tool name explicitly states 'remove' and description confirms 'Removes a queue tree entry' - this is an irreversible deletion operation on router configuration that cannot be undone without manual reconfiguration.
Attacks that exploit this kind of access
The rule that runs mikrotik_remove_queue_tree 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_queue_tree, this is the rule to start with:
mikrotik_remove_queue_tree is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect MikroTik Cursor MCP, apply this rule, and every mikrotik_remove_queue_tree call is checked against it from then on.
Questions about mikrotik_remove_queue_tree
Removes a queue tree entry. 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_queue_tree: 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_queue_tree 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_queue_tree 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_queue_tree. 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_queue_tree 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.
More on MikroTik Cursor, and thousands of servers like it.
Across the catalogue