Creates a DHCPv6 client
AI agents use mikrotik_create_dhcpv6_client 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.
Creating a DHCPv6 client is a reversible configuration change to a MikroTik router. It modifies network settings but does not delete, execute arbitrary commands, or move funds. The severity is medium because misconfiguration could disrupt IPv6 connectivity or network operations, but the action itself is non-destructive and can be undone by removing the DHCPv6 client configuration.
From the tool's definition Tool name 'mikrotik_create_dhcpv6_client' explicitly indicates creation of a network configuration object. Description confirms 'Creates a DHCPv6 client'.
Attacks that exploit this kind of access
Creates a DHCPv6 client. 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_create_dhcpv6_client: 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_create_dhcpv6_client 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_create_dhcpv6_client 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_create_dhcpv6_client. 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_create_dhcpv6_client 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 →