list_ssh_keys
AI agents call list_ssh_keys to retrieve information from Nebulablock without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves SSH key metadata for display/audit purposes with no side effects. While SSH keys are sensitive credentials, listing them is a read-only operation with minimal blast radius if an AI agent misuses it—it cannot create, modify, or delete keys. Confidence is slightly reduced due to the empty description, but the naming convention and sibling context strongly indicate read semantics.
From the tool's definition Tool name 'list_ssh_keys' indicates a retrieval operation. Despite empty description, the 'list' prefix and context among sibling tools (get_user_instances, get_user_credit_balance) clearly indicate this fetches or enumerates existing SSH keys without…
Attacks that exploit this kind of access
list_ssh_keys. It is categorised as a Read tool in the Nebulablock MCP Server, which means it retrieves data without modifying state.
Register the Nebulablock MCP server in PolicyLayer and add a rule for list_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 Nebulablock. Nothing to install.
list_ssh_keys 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 list_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 list_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.
list_ssh_keys is provided by the Nebulablock MCP server (nebula-block-data/nebulablock-mcp-server). 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 →