Force VRRP interface to become master (sets priority to 255)
AI agents invoke mikrotik_force_vrrp_master to trigger actions in MikroTik Cursor MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool actively triggers a network topology change by forcing a VRRP failover, causing one router to take over as master. This is an external operational effect on live network infrastructure — it can disrupt traffic routing and high-availability setups. It modifies runtime state and triggers failover behavior, making it Execute.
From the tool's definition Force VRRP interface to become master (sets priority to 255)
Attacks that exploit this kind of access
Force VRRP interface to become master (sets priority to 255). It is categorised as a Execute tool in the MikroTik Cursor MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MikroTik Cursor MCP server in PolicyLayer and add a rule for mikrotik_force_vrrp_master: 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_force_vrrp_master is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the mikrotik_force_vrrp_master 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_force_vrrp_master. 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_force_vrrp_master 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 →