Fetch a fresh download URL for the SSH private key. Use this if the key was corrupted during initial save (e.g., "error in libcrypto" when running ssh-keygen -y -f <keyfile>).
Part of the Autodock server.
Free to start. No card required.
AI agents use env.get_ssh_key to create or modify resources in Autodock. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call env.get_ssh_key repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Autodock.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"env.get_ssh_key": {
"limits": [
{
"counter": "env.get_ssh_key_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Autodock policy for all 27 tools.
These attack patterns abuse exactly the kind of access env.get_ssh_key gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Fetch a fresh download URL for the SSH private key. Use this if the key was corrupted during initial save (e.g., "error in libcrypto" when running ssh-keygen -y -f <keyfile>).. It is categorised as a Write tool in the Autodock MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Autodock MCP server in PolicyLayer and add a rule for env.get_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 Autodock. Nothing to install.
env.get_ssh_key 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 env.get_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.
Set action: deny in the PolicyLayer policy for env.get_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.
env.get_ssh_key is provided by the Autodock MCP server (mikesol/autodock). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 27 Autodock tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.