ssh
Run a RouterOS command over SSH using MIKROTIK_* credentials.
This record as markdown: /tools/mcp-control-plane/ssh.md
What ssh does on Mcp Control Plane
AI agents invoke ssh to trigger actions in Mcp Control Plane. 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.
Why ssh is rated High
This tool executes commands on a MikroTik RouterOS device via SSH. Command execution is classified as Execute rather than Read because the tool can run any RouterOS command with side effects that depend on the arguments supplied—including configuration changes, network resets, service restarts, or traffic manipulation.
From the tool's definition Tool explicitly states it 'Run[s] a RouterOS command over SSH', which executes arbitrary commands on a network device.
Attacks that exploit this kind of access
The rule that runs ssh safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ssh, this is the rule to start with:
ssh stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Control Plane, apply this rule, and every ssh call is checked against it from then on.
Questions about ssh
Run a RouterOS command over SSH using MIKROTIK_* credentials. It is categorised as a Execute tool in the Mcp Control Plane MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for 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 Mcp Control Plane. Nothing to install.
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 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 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.
ssh is provided by the Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Control Plane, and thousands of servers like it.
Across the catalogue