router_health

Return a compact RouterOS health summary with computed warnings.

SERVERMcp Control Plane SOURCEalbertik322-sudo/mcp-control-plane

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mcp-control-plane/router-health.md

WHAT IT DOES

What router_health does on Mcp Control Plane

AI agents call router_health 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.

RISK

Why router_health is rated Low

The tool retrieves and summarizes router health metrics from RouterOS (MikroTik). This is a read-only operation that queries system state and may compute warnings but does not create, modify, delete, or execute code. It has minimal blast radius if misused—an AI agent calling it repeatedly would only generate excess queries, not cause damage.

From the tool's definition Tool name is 'router_health' and description states it returns a 'health summary' - a query/retrieval operation that computes and returns status information without modifying any state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs router_health 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 router_health, this is the rule to start with:

router_health Allowed

router_health is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "router_health": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Control Plane, apply this rule, and every router_health call is checked against it from then on.

FAQ

Questions about router_health

What does the router_health tool do? +

Return a compact RouterOS health summary with computed warnings. It is categorised as a Read tool in the Mcp Control Plane MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on router_health? +

Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for router_health: 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.

What risk level is router_health? +

router_health is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit router_health? +

Yes. Add a rate_limit block to the router_health 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.

How do I block router_health completely? +

Set action: deny in the PolicyLayer policy for router_health. 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.

What MCP server provides router_health? +

router_health 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.

KEEP EXPLORING

More on Mcp Control Plane, and thousands of servers like it.

This server

All 286 Mcp Control Plane tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →