Removes a NAT rule from MikroTik device
AI agents call mikrotik_remove_nat_rule to permanently remove resources in MikroTik MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing NAT rules is a destructive operation that cannot be undone without manual re-creation or backup restoration. NAT rules are critical network infrastructure; their removal can cause immediate network connectivity issues, service outages, and broken routing for dependent systems. The blast radius is high because incorrect removal affects all traffic flows dependent on that rule.
From the tool's definition Tool name contains 'remove' and description explicitly states 'Removes a NAT rule from MikroTik device' — deletion is irreversible network configuration change.
Attacks that exploit this kind of access
Removes a NAT rule from MikroTik device. It is categorised as a Destructive tool in the MikroTik MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MikroTik MCP server in PolicyLayer and add a rule for mikrotik_remove_nat_rule: 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_remove_nat_rule 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_nat_rule 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_nat_rule. 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_nat_rule 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 →