run_router_health_report

运行路由体检

SERVERIkuai SOURCEgxxHuang/ikuai-mcp-server

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ikuai-mcp-server/run-router-health-report.md

WHAT IT DOES

What run_router_health_report does on Ikuai

AI agents invoke run_router_health_report to trigger actions in Ikuai. 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.

RISK

Why run_router_health_report is rated High

run_router_health_report triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_router_health_report safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ikuai, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_router_health_report, this is the rule to start with:

run_router_health_report Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_router_health_report": {
      "limits": [
        {
          "counter": "run_router_health_report_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about run_router_health_report

What does the run_router_health_report tool do? +

运行路由体检. It is categorised as a Execute tool in the Ikuai MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_router_health_report? +

Register the Ikuai MCP server in PolicyLayer and add a rule for run_router_health_report: 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 Ikuai. Nothing to install.

What risk level is run_router_health_report? +

run_router_health_report is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_router_health_report? +

Yes. Add a rate_limit block to the run_router_health_report 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 run_router_health_report completely? +

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

run_router_health_report is provided by the Ikuai MCP server (gxxHuang/ikuai-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ikuai, and thousands of servers like it.

This server

All 229 Ikuai tools → High-risk tools on this server →

Across the catalogue

shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →