This record as markdown: /tools/ikuai-mcp-server/get-diversion-monitoring.md
What get_diversion_monitoring does on Ikuai
AI agents call get_diversion_monitoring to retrieve information from Ikuai without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_diversion_monitoring is rated Low
This tool retrieves monitoring status information about traffic diversion/load balancing on the iKuai router. No data is created, modified, deleted, or executed — it only queries and returns current state. This is a standard Read operation with minimal security risk unless the returned data is sensitive, but exposure of monitoring status is typically low-impact compared to configuration changes or command execution.
From the tool's definition Tool name 'get_diversion_monitoring' with description '获取分流监控状态' (get diversion monitoring status). The 'get_' prefix and '获取' (retrieve/fetch) action indicate a read-only query operation.
Attacks that exploit this kind of access
The rule that runs get_diversion_monitoring 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 get_diversion_monitoring, this is the rule to start with:
get_diversion_monitoring 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 Ikuai, apply this rule, and every get_diversion_monitoring call is checked against it from then on.
Questions about get_diversion_monitoring
获取分流监控状态. It is categorised as a Read tool in the Ikuai MCP Server, which means it retrieves data without modifying state.
Register the Ikuai MCP server in PolicyLayer and add a rule for get_diversion_monitoring: 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.
get_diversion_monitoring 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 get_diversion_monitoring 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 get_diversion_monitoring. 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.
get_diversion_monitoring 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.
More on Ikuai, and thousands of servers like it.
This server
Across the catalogue