AI agents invoke interrupt to trigger actions in Ssh. 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.
Sending Ctrl+C sends an interrupt signal (SIGINT) to the active process in the SSH session, terminating or interrupting whatever is currently running. This is an execution-side-effect operation — it actively interferes with running processes.
From the tool's definition Send Ctrl+C to the session
Attacks that exploit this kind of access
Send Ctrl+C to the session. It is categorised as a Execute tool in the Ssh MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ssh MCP server in PolicyLayer and add a rule for interrupt: 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. Nothing to install.
interrupt 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 interrupt 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 interrupt. 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.
interrupt is provided by the Ssh MCP server (sc-ml-cmd/ssh-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 →