Execute SSH protocol operations. Supports password and key-based authentication for Linux/Unix hosts.
AI agents invoke cme_ssh to trigger actions in CrackMapExec 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.
SSH authentication and command execution constitute the Execute category—triggering external operations whose effects depend on arguments. Given the context of a penetration testing framework (CrackMapExec/NetExec) with credential support, this tool could execute arbitrary commands on remote systems with severe blast radius.
From the tool's definition The tool description explicitly states it 'Execute[s] SSH protocol operations' and supports 'authentication for Linux/Unix hosts,' enabling command execution on remote systems.
Attacks that exploit this kind of access
Execute SSH protocol operations. Supports password and key-based authentication for Linux/Unix hosts. It is categorised as a Execute tool in the CrackMapExec MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the CrackMapExec MCP Server MCP server in PolicyLayer and add a rule for cme_ssh: 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 CrackMapExec MCP Server. Nothing to install.
cme_ssh 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 cme_ssh 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 cme_ssh. 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.
cme_ssh is provided by the CrackMapExec MCP Server MCP server (schwarztim/sec-crackmapexec-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 →