probe
Check common RouterOS management ports without logging in.
This record as markdown: /tools/mcp-control-plane/probe.md
What probe does on Mcp Control Plane
AI agents call probe to retrieve information from Mcp Control Plane without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why probe is rated Low
This is a passive reconnaissance tool that queries the availability and status of management ports on RouterOS devices. It performs no side effects, makes no modifications, executes no commands, and only retrieves information about port accessibility. The explicit mention of 'without logging in' confirms it does not alter state. This is characteristic of Read category tools (list, fetch, check).
From the tool's definition Tool name 'probe' and description 'Check common RouterOS management ports without logging in' indicate non-invasive port/service discovery with no authentication required, no data modification, and no command execution.
Attacks that exploit this kind of access
The rule that runs probe 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 probe, this is the rule to start with:
probe is read-only, so it stays allowed. 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 probe call is checked against it from then on.
Questions about probe
Check common RouterOS management ports without logging in. It is categorised as a Read tool in the Mcp Control Plane MCP Server, which means it retrieves data without modifying state.
Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for probe: 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.
probe is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the probe 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 probe. 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.
probe 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.
This server
Across the catalogue