Lists DHCPv6 options
AI agents call mikrotik_list_dhcpv6_options 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.
The 'list' operation retrieves DHCPv6 option configurations from the MikroTik router. This is a non-destructive read operation with no side effects. Even in a compromised scenario where an AI agent misuses this tool, the blast radius is minimal—the attacker gains only visibility into DHCPv6 settings, which does not alter router state or enable lateral movement beyond information disclosure.
From the tool's definition Tool name contains 'list' and description states 'Lists DHCPv6 options' — a pure query operation that retrieves configuration data without modification.
Attacks that exploit this kind of access
Lists DHCPv6 options. 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_dhcpv6_options: 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_dhcpv6_options 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_dhcpv6_options 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_dhcpv6_options. 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_dhcpv6_options 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 →