Quick health check of Claude Code conversations. Reports total issues, largest files, and recommendations.
AI agents call health_check to retrieve information from Claude Code Toolkit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the state of Claude Code conversations and returns diagnostic information (total issues, largest files, recommendations). It is observational in nature with no side effects—no data is created, modified, deleted, or executed. This aligns with the Read category for retrieval and query operations.
From the tool's definition Tool is described as performing a 'health check' that 'reports' metrics and 'recommendations' with no mention of modification, deletion, or execution capabilities. The verb 'reports' indicates data retrieval and analysis only.
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 Claude Code Toolkit, 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.
Quick health check of Claude Code conversations. Reports total issues, largest files, and recommendations. It is categorised as a Read tool in the Claude Code Toolkit MCP Server, which means it retrieves data without modifying state.
Register the Claude Code Toolkit 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 Claude Code Toolkit. 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 Claude Code Toolkit MCP server (asifkibria/claude-code-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude Code Toolkit, 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.
40 Claude Code Toolkit tools catalogued and risk-classified — across an index of 43,000+ MCP servers.