Gets IPv6 ND settings for interface
AI agents call mikrotik_get_ipv6_nd_settings 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 queries IPv6 Neighbor Discovery settings from a MikroTik router interface. It is a read-only operation that retrieves data with no side effects, no code execution, and no modifications to system state. Even in the context of router management via SSH/API, passive querying of interface settings poses minimal risk.
From the tool's definition Tool name contains 'get' and description states 'Gets IPv6 ND settings for interface' — retrieves configuration data without modification or execution of commands.
Attacks that exploit this kind of access
Gets IPv6 ND settings for interface. 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_get_ipv6_nd_settings: 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_get_ipv6_nd_settings 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_get_ipv6_nd_settings 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_get_ipv6_nd_settings. 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_get_ipv6_nd_settings 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 →