AI agents invoke ssh_trust_host to trigger actions in Unlimited. 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.
Trusting an SSH host modifies the SSH known_hosts configuration, which is a security-sensitive operation that enables future connections to that host. This is at minimum a Write operation modifying system security configuration, but since it involves establishing trust for external connections and could be exploited to MITM attacks, it warrants Execute severity. The empty description lowers confidence significantly.
From the tool's definition Tool name 'ssh_trust_host' and sibling tool 'add_host' suggest this adds an SSH host to known_hosts or trusted hosts list, triggering an external security operation. Description is empty.
Attacks that exploit this kind of access
ssh_trust_host. It is categorised as a Execute tool in the Unlimited MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Unlimited MCP server in PolicyLayer and add a rule for ssh_trust_host: 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 Unlimited. Nothing to install.
ssh_trust_host 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 ssh_trust_host 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 ssh_trust_host. 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.
ssh_trust_host is provided by the Unlimited MCP server (triumsebas/unlimited-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →