revoke_cert

Revoke an issued SSH certificate.

SERVERSSH MCP Server SOURCEbhayanak/ssh-mcp-server

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/bhayanak-ssh-mcp-server/revoke-cert.md

WHAT IT DOES

What revoke_cert does on SSH MCP Server

AI agents call revoke_cert to permanently remove resources in SSH MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why revoke_cert is rated Critical

Revoking a certificate is an irreversible action that permanently invalidates an SSH certificate. Once revoked, the certificate cannot be un-revoked, potentially locking users or systems out of remote access. This constitutes a destructive, non-reversible operation with high blast radius if misused by an AI agent.

From the tool's definition Revoke an issued SSH certificate

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs revoke_cert safely

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

revoke_cert Hidden

revoke_cert is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "revoke_cert"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about revoke_cert

What does the revoke_cert tool do? +

Revoke an issued SSH certificate. It is categorised as a Destructive tool in the SSH MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on revoke_cert? +

Register the SSH MCP Server MCP server in PolicyLayer and add a rule for revoke_cert: 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 SSH MCP Server. Nothing to install.

What risk level is revoke_cert? +

revoke_cert is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit revoke_cert? +

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

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

revoke_cert is provided by the SSH MCP Server MCP server (bhayanak/ssh-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on SSH MCP Server, and thousands of servers like it.

This server

All 23 SSH MCP Server tools → Critical-risk tools on this server →

Across the catalogue

web3_revoke_key on 0xarchive →revoke_api_token on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →