chaoxing_read_detection_status

Read live parse and payment status for one detection record.

SERVERChaoxing Agent SOURCECr-GH0/chaoxing-agent

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/chaoxing-agent/chaoxing-read-detection-status.md

WHAT IT DOES

What chaoxing_read_detection_status does on Chaoxing Agent

AI agents call chaoxing_read_detection_status to retrieve information from Chaoxing Agent without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why chaoxing_read_detection_status is rated Low

Even though chaoxing_read_detection_status only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs chaoxing_read_detection_status safely

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

chaoxing_read_detection_status Allowed

chaoxing_read_detection_status 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": {
    "chaoxing_read_detection_status": {}
  }
}

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

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

FAQ

Questions about chaoxing_read_detection_status

What does the chaoxing_read_detection_status tool do? +

Read live parse and payment status for one detection record. It is categorised as a Read tool in the Chaoxing Agent MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on chaoxing_read_detection_status? +

Register the Chaoxing Agent MCP server in PolicyLayer and add a rule for chaoxing_read_detection_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 Chaoxing Agent. Nothing to install.

What risk level is chaoxing_read_detection_status? +

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

Can I rate-limit chaoxing_read_detection_status? +

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

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

chaoxing_read_detection_status is provided by the Chaoxing Agent MCP server (Cr-GH0/chaoxing-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Chaoxing Agent, and thousands of servers like it.

This server

All 565 Chaoxing Agent tools →

Across the catalogue

read_input_file on 0gzk →claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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