check_status

check_status

Server Xadeus-QQ-MCP mouse114514/xadeus-qq-mcp
Category Read
Risk class Low
Parameters 00 required

What check_status does on Xadeus-QQ-MCP

AI agents call check_status to retrieve information from Xadeus-QQ-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why check_status needs a policy

The tool name 'check_status' strongly suggests a read-only operation that retrieves the current state of the QQ connection or service without modifying data. Given the QQ messaging server context and the presence of other read tools (get_*), this most likely queries connection status, online status, or service health.

From the tool's definition Tool name 'check_status' combined with sibling tools (get_friend_list, get_group_list, etc.) indicates a query/read operation typical of status monitoring systems. No description provided, so classification relies on naming convention and context.

Questions about check_status

What does the check_status tool do? +

check_status. It is categorised as a Read tool in the Xadeus-QQ-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_status? +

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

What risk level is check_status? +

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

Can I rate-limit check_status? +

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

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

check_status is provided by the Xadeus-QQ- MCP server (mouse114514/xadeus-qq-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

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.