Disables a firewall filter rule
AI agents use mikrotik_disable_filter_rule to create or update resources in MikroTik Cursor MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MikroTik Cursor MCP environment.
Disabling a firewall filter rule modifies the router's security posture reversibly (the rule still exists but is inactive). This is a Write operation since it changes state without permanently deleting anything. However, the severity is high because disabling firewall rules can expose the network to traffic that was previously blocked, potentially allowing unauthorized access or attacks.
From the tool's definition Disables a firewall filter rule
Attacks that exploit this kind of access
Disables a firewall filter rule. It is categorised as a Write tool in the MikroTik Cursor MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MikroTik Cursor MCP server in PolicyLayer and add a rule for mikrotik_disable_filter_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 Cursor MCP. Nothing to install.
mikrotik_disable_filter_rule 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_filter_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_disable_filter_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_disable_filter_rule 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 →