issue_cert
Issue a short-lived SSH certificate for a user.
This record as markdown: /tools/bhayanak-ssh-mcp-server/issue-cert.md
What issue_cert does on SSH MCP Server
AI agents use issue_cert to create or update resources in SSH MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SSH MCP Server environment.
Why issue_cert is rated Medium
Issuing an SSH certificate creates a new credential that grants a user SSH access to remote systems. While the certificate is short-lived (somewhat reversible in effect), the act of creation is a Write operation. The severity is high because misuse could grant unauthorized access to remote Linux servers, but it doesn't directly execute commands or irreversibly destroy data.
From the tool's definition Issue a short-lived SSH certificate for a user
Attacks that exploit this kind of access
The rule that runs issue_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 issue_cert, this is the rule to start with:
issue_cert 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.
The button opens the PolicyLayer dashboard: create your workspace, connect SSH MCP Server, apply this rule, and every issue_cert call is checked against it from then on.
Questions about issue_cert
Issue a short-lived SSH certificate for a user. It is categorised as a Write tool in the SSH MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SSH MCP Server MCP server in PolicyLayer and add a rule for issue_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.
issue_cert is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the issue_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.
Set action: deny in the PolicyLayer policy for issue_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.
issue_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.
More on SSH MCP Server, and thousands of servers like it.
This server
Across the catalogue