Close an interactive shell session
AI agents invoke ssh_close_interactive_shell to trigger actions in SSH MCP Server. 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.
Closing an interactive shell session terminates an active process/session on a remote system. This is an Execute-category action as it triggers an external operation (terminating a shell session) on a remote server. While it doesn't delete data, it does affect running state on the remote system.
From the tool's definition Close an interactive shell session
Attacks that exploit this kind of access
Close an interactive shell session. It is categorised as a Execute tool in the SSH MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SSH MCP Server MCP server in PolicyLayer and add a rule for ssh_close_interactive_shell: 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.
ssh_close_interactive_shell 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_close_interactive_shell 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_close_interactive_shell. 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_close_interactive_shell is provided by the SSH MCP Server MCP server (widjis/mcp-ssh). 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 →