Enables IGMP snooping on a bridge
AI agents use mikrotik_enable_igmp_snooping 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.
This tool modifies bridge configuration by enabling IGMP snooping, which is a reversible network setting change. It does not execute arbitrary code, delete data, or move money. The blast radius is medium because misconfiguration of IGMP snooping could impact multicast traffic handling and network performance, but the change can be undone by disabling the setting.
From the tool's definition Tool name 'mikrotik_enable_igmp_snooping' and description 'Enables IGMP snooping on a bridge' indicate configuration modification of network bridge settings.
Attacks that exploit this kind of access
Enables IGMP snooping on a bridge. 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_enable_igmp_snooping: 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_enable_igmp_snooping 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_enable_igmp_snooping 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_enable_igmp_snooping. 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_enable_igmp_snooping 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 →