New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_diversion_monitoring

获取分流监控状态

SERVERIkuai SOURCEgxxHuang/ikuai-mcp-server
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/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.

Questions about get_diversion_monitoring

What does the get_diversion_monitoring tool do? +

获取分流监控状态. It is categorised as a Read tool in the Ikuai MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_diversion_monitoring? +

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.

What risk level is get_diversion_monitoring? +

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

Can I rate-limit get_diversion_monitoring? +

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.

How do I block get_diversion_monitoring completely? +

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.

What MCP server provides get_diversion_monitoring? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Ikuai's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.