Lists IPv6 neighbors
AI agents call mikrotik_list_ipv6_neighbors to retrieve information from MikroTik Cursor MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about IPv6 neighbors on MikroTik routers. It performs a read-only query operation that returns existing data without side effects. Even in the context of router management, listing neighbors is non-destructive intelligence gathering.
From the tool's definition Tool name 'mikrotik_list_ipv6_neighbors' and description 'Lists IPv6 neighbors' indicate a query/retrieval operation with no data modification, deletion, or execution of arbitrary commands.
Attacks that exploit this kind of access
Lists IPv6 neighbors. It is categorised as a Read tool in the MikroTik Cursor MCP MCP Server, which means it retrieves data without modifying state.
Register the MikroTik Cursor MCP server in PolicyLayer and add a rule for mikrotik_list_ipv6_neighbors: 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_list_ipv6_neighbors is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the mikrotik_list_ipv6_neighbors 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_list_ipv6_neighbors. 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_list_ipv6_neighbors 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 →