AI agents call health_check to retrieve information from CC Web MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs diagnostic checks on infrastructure (dependencies, configuration, network status) and only reads/reports existing state. It has no capability to modify data, execute arbitrary code, delete resources, or initiate financial transactions.
From the tool's definition Tool name 'health_check' and description '检查 MCP 依赖、配置和网络连通性' (Check MCP dependencies, configuration and network connectivity) indicate a diagnostic/monitoring function that queries system state without modification.
Documented attack patterns abuse exactly the kind of access health_check gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CC Web MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for health_check:
{
"version": "1",
"default": "deny",
"tools": {
"health_check": {}
}
}health_check is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
检查 MCP 依赖、配置和网络连通性。. It is categorised as a Read tool in the CC Web MCP MCP Server, which means it retrieves data without modifying state.
Register the CC Web MCP server in PolicyLayer and add a rule for health_check: 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 CC Web MCP. Nothing to install.
health_check 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 health_check 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 health_check. 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.
health_check is provided by the CC Web MCP server (jcdizzy/cc-web-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CC Web MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 CC Web MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.