Sets SSH public keys for a user
AI agents use mikrotik_set_user_ssh_keys 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 user authentication material (SSH public keys) reversibly. While credential manipulation carries significant risk (an attacker could lock out legitimate users or add backdoor access), it is classified as Write rather than Execute or Destructive because: (1) the operation itself is a data modification, not execution of arbitrary code; (2) it is theoretically reversible by re-setting keys to correct…
From the tool's definition Tool name contains 'set' and description states 'Sets SSH public keys for a user' — this is a modification operation that creates or updates user authentication credentials.
Attacks that exploit this kind of access
Sets SSH public keys for a user. 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_set_user_ssh_keys: 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_set_user_ssh_keys 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_set_user_ssh_keys 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_set_user_ssh_keys. 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_set_user_ssh_keys 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 →