Remove bonding interface
AI agents call mikrotik_remove_bonding_interface 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.
Removing a bonding interface is a destructive operation that cannot be undone without manual reconfiguration. It destroys network interface aggregation settings, potentially disrupting network connectivity and requiring manual intervention to restore. This is more severe than Write operations since the change is not easily reversible and affects critical infrastructure.
From the tool's definition Tool name explicitly contains 'remove' and description states 'Remove bonding interface' — this irreversibly deletes network interface configuration.
Attacks that exploit this kind of access
Remove bonding interface. 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_bonding_interface: 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_bonding_interface 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_bonding_interface 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_bonding_interface. 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_bonding_interface 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 →