rename_ssh_key · Nebulablock MCP: Risk & Policy

WHAT IT DOES

What rename_ssh_key does on Nebulablock

AI agents use rename_ssh_key to create or update resources in Nebulablock — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nebulablock environment.

WHY IT NEEDS A POLICY

Why rename_ssh_key needs a policy

Renaming an SSH key is a reversible modification operation that updates metadata without deleting the underlying cryptographic material or executing commands. This is a Write action. Severity is medium because misuse could aid in obscuring key ownership or confusing key management, though the operation itself is non-destructive.

From the tool's definition Tool name 'rename_ssh_key' indicates modification of SSH key metadata. Server context shows GPU/compute instance management with API keys and SSH key operations (create_ssh_key, delete_ssh_key siblings).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename_ssh_key Rate-limited

rename_ssh_key stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rename_ssh_key": {
      "limits": [
        {
          "counter": "rename_ssh_key_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Nebulablock, so you can run agents against it safely.

FAQ

Questions about rename_ssh_key

What does the rename_ssh_key tool do? +

rename_ssh_key. It is categorised as a Write tool in the Nebulablock MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on rename_ssh_key? +

Register the Nebulablock MCP server in PolicyLayer and add a rule for rename_ssh_key: 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.

What risk level is rename_ssh_key? +

rename_ssh_key is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit rename_ssh_key? +

Yes. Add a rate_limit block to the rename_ssh_key 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 rename_ssh_key completely? +

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

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