run
Run a terminal-like RouterOS command through the API, for example '/system resource print'.
This record as markdown: /tools/mcp-control-plane/run.md
What run does on Mcp Control Plane
AI agents invoke run 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 run is rated High
This tool allows execution of RouterOS API commands with outcomes dependent on the supplied arguments. RouterOS commands can modify network configuration, restart services, or alter system state. While not inherently destructive (the tool itself doesn't force destructive operations), it executes external commands whose effects are not sandboxed, making it Execute rather than Write.
From the tool's definition 'Run a terminal-like RouterOS command through the API' — the tool executes arbitrary commands in a RouterOS/MikroTik environment with side effects determined by the command argument.
Attacks that exploit this kind of access
The rule that runs run 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 run, this is the rule to start with:
run 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 run call is checked against it from then on.
Questions about run
Run a terminal-like RouterOS command through the API, for example '/system resource print'. 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 run: 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.
run 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 run 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 run. 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.
run 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