credentials_rotate_ssh
Run credentials.rotate-ssh through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/credentials-rotate-ssh.md
What credentials_rotate_ssh does on Appaloft
AI agents invoke credentials_rotate_ssh to trigger actions in Appaloft. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
username | object | — | |
publicKey | object | — | |
privateKey | string | Yes | |
confirmation | object | Yes | |
credentialId | string | Yes | |
idempotencyKey | string | — |
Parameters from the server's own tool schema.
Why credentials_rotate_ssh is rated High
SSH credential rotation is an Execute-class action because it triggers an external operation (credential rotation in Appaloft) whose effects depend on arguments and system state. While it modifies credentials (potentially Write-adjacent), the primary action is running/executing a catalog operation.
From the tool's definition Tool name 'credentials_rotate_ssh' and description 'Run credentials.rotate-ssh through the Appaloft application operation catalog' indicate execution of a credential rotation operation.
Attacks that exploit this kind of access
The rule that runs credentials_rotate_ssh safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Appaloft, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For credentials_rotate_ssh, this is the rule to start with:
credentials_rotate_ssh stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Appaloft, apply this rule, and every credentials_rotate_ssh call is checked against it from then on.
Questions about credentials_rotate_ssh
Run credentials.rotate-ssh through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Execute tool in the Appaloft MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
credentials_rotate_ssh accepts 6 parameters: username, publicKey, privateKey, confirmation, credentialId, idempotencyKey. Required: privateKey, confirmation, credentialId. The full parameter table on this page comes from the server's own tool schema.
Register the Appaloft MCP server in PolicyLayer and add a rule for credentials_rotate_ssh: 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 Appaloft. Nothing to install.
credentials_rotate_ssh is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the credentials_rotate_ssh 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 credentials_rotate_ssh. 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.
credentials_rotate_ssh is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Appaloft, and thousands of servers like it.
Across the catalogue