mikrotik_list_user_ssh_keys

Lists SSH keys for a specific user

SERVERMikroTik Cursor MCP SOURCEkevinpez/mikrotik-cursor-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kevinpez-mikrotik-cursor-mcp/mikrotik-list-user-ssh-keys.md

WHAT IT DOES

What mikrotik_list_user_ssh_keys does on MikroTik Cursor MCP

AI agents call mikrotik_list_user_ssh_keys to retrieve information from MikroTik Cursor MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why mikrotik_list_user_ssh_keys is rated Low

This tool performs a query operation to retrieve existing SSH key information for auditing or administrative purposes. Listing data is non-destructive and does not modify system state. While SSH keys are sensitive credentials, merely listing them (presumably for an authenticated admin) is a read-only operation.

From the tool's definition Tool name contains 'list' and description explicitly states 'Lists SSH keys for a specific user' — a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mikrotik_list_user_ssh_keys safely

PolicyLayer is an MCP gateway: it sits between your AI agents and MikroTik Cursor MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mikrotik_list_user_ssh_keys, this is the rule to start with:

mikrotik_list_user_ssh_keys Allowed

mikrotik_list_user_ssh_keys is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mikrotik_list_user_ssh_keys": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect MikroTik Cursor MCP, apply this rule, and every mikrotik_list_user_ssh_keys call is checked against it from then on.

FAQ

Questions about mikrotik_list_user_ssh_keys

What does the mikrotik_list_user_ssh_keys tool do? +

Lists SSH keys for a specific user. It is categorised as a Read tool in the MikroTik Cursor MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mikrotik_list_user_ssh_keys? +

Register the MikroTik Cursor MCP server in PolicyLayer and add a rule for mikrotik_list_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.

What risk level is mikrotik_list_user_ssh_keys? +

mikrotik_list_user_ssh_keys is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit mikrotik_list_user_ssh_keys? +

Yes. Add a rate_limit block to the mikrotik_list_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.

How do I block mikrotik_list_user_ssh_keys completely? +

Set action: deny in the PolicyLayer policy for mikrotik_list_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.

What MCP server provides mikrotik_list_user_ssh_keys? +

mikrotik_list_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.

KEEP EXPLORING

More on MikroTik Cursor, and thousands of servers like it.

This server

All 452 MikroTik Cursor tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →