# create_private_key

Create a new SSH private key.

Agent View of the PolicyLayer registry record for `create_private_key`. HTML page: https://policylayer.com/tools/coolify/create-private-key

## Facts

- Tool: `create_private_key`
- Server: Coolify (`coolify-mcp-server`) — https://policylayer.com/tools/coolify.md
- Install: `npx -y coolify-mcp-server`
- Homepage: git+https://github.com/wrediam/coolify-mcp-server.git
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "create_private_key",
    "arguments": {}
  }
}
```

## Why create_private_key is rated Medium

Creating SSH private keys is a reversible Write operation (keys can be deleted or rotated), but rated high severity because misuse could generate credentials that compromise infrastructure security. An AI agent creating uncontrolled private keys could enable unauthorized access to systems.

From the tool's own definition: "Tool named 'create_private_key' with description 'Create a new SSH private key.' – this creates and stores cryptographic material."

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Coolify:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_private_key": {
      "limits": [
        {
          "counter": "create_private_key_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Coolify (110)

- `delete_application` — Destructive — https://policylayer.com/tools/coolify/delete-application.md
- `delete_application_env` — Destructive — https://policylayer.com/tools/coolify/delete-application-env.md
- `delete_application_scheduled_task` — Destructive — https://policylayer.com/tools/coolify/delete-application-scheduled-task.md
- `delete_application_storage` — Destructive — https://policylayer.com/tools/coolify/delete-application-storage.md
- `delete_cloud_token` — Destructive — https://policylayer.com/tools/coolify/delete-cloud-token.md
- `delete_database` — Destructive — https://policylayer.com/tools/coolify/delete-database.md
- `delete_database_env` — Destructive — https://policylayer.com/tools/coolify/delete-database-env.md
- `delete_environment` — Destructive — https://policylayer.com/tools/coolify/delete-environment.md
- `delete_github_app` — Destructive — https://policylayer.com/tools/coolify/delete-github-app.md
- `delete_private_key` — Destructive — https://policylayer.com/tools/coolify/delete-private-key.md
- `delete_project` — Destructive — https://policylayer.com/tools/coolify/delete-project.md
- `delete_server` — Destructive — https://policylayer.com/tools/coolify/delete-server.md
- `delete_service` — Destructive — https://policylayer.com/tools/coolify/delete-service.md
- `delete_service_env` — Destructive — https://policylayer.com/tools/coolify/delete-service-env.md
- `delete_service_scheduled_task` — Destructive — https://policylayer.com/tools/coolify/delete-service-scheduled-task.md
- `disable_api` — Destructive — https://policylayer.com/tools/coolify/disable-api.md
- `cancel_deployment` — Execute — https://policylayer.com/tools/coolify/cancel-deployment.md
- `deploy_by_tag_or_uuid` — Execute — https://policylayer.com/tools/coolify/deploy-by-tag-or-uuid.md
- `enable_api` — Execute — https://policylayer.com/tools/coolify/enable-api.md
- `restart_application` — Execute — https://policylayer.com/tools/coolify/restart-application.md
- `restart_database` — Execute — https://policylayer.com/tools/coolify/restart-database.md
- `restart_service` — Execute — https://policylayer.com/tools/coolify/restart-service.md
- `start_application` — Execute — https://policylayer.com/tools/coolify/start-application.md
- `start_database` — Execute — https://policylayer.com/tools/coolify/start-database.md
- `start_service` — Execute — https://policylayer.com/tools/coolify/start-service.md
- `stop_application` — Execute — https://policylayer.com/tools/coolify/stop-application.md
- `stop_database` — Execute — https://policylayer.com/tools/coolify/stop-database.md
- `stop_service` — Execute — https://policylayer.com/tools/coolify/stop-service.md
- `get_application` — Read — https://policylayer.com/tools/coolify/get-application.md
- `get_application_logs` — Read — https://policylayer.com/tools/coolify/get-application-logs.md
- …and 80 more: https://policylayer.com/tools/coolify.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=coolify · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/coolify