Deep validation of all Claude Code configuration files. Catches real problems before they cause confusing behavior in Claude Code sessions. Checks performed: • CLAUDE.md: Exists, not empty, starts with heading, under 500 lines • Skills: Valid YAML frontmatter, required 'name' and 'description' fi...
Part of the Ccboot server.
Free to start. No card required.
AI agents call ccboot_validate_config to retrieve information from Ccboot without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though ccboot_validate_config only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"ccboot_validate_config": {}
}
}See the full Ccboot policy for all 16 tools.
These attack patterns abuse exactly the kind of access ccboot_validate_config gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Deep validation of all Claude Code configuration files. Catches real problems before they cause confusing behavior in Claude Code sessions. Checks performed: • CLAUDE.md: Exists, not empty, starts with heading, under 500 lines • Skills: Valid YAML frontmatter, required 'name' and 'description' fields, name under 64 chars, description under 200 chars • Settings: Valid JSON, proper hook structure • .mcp.json: Valid JSON structure • Agents: Files exist and are readable auto_fix mode can repair: • Trailing commas in JSON • Missing frontmatter fields (adds placeholders) CI mode (ci_mode: true): • Forces JSON output format for machine readability • Returns isError: true when validation fails (exit code 1 in CLI) • Ideal for CI/CD pipelines and pre-commit hooks Examples: ccboot_validate_config({ project_path: '.', fix_mode: 'report' }) ccboot_validate_config({ project_path: '.', fix_mode: 'auto_fix' }) ccboot_validate_config({ project_path: '.', ci_mode: true }) Returns: Validation report with errors, warnings, and applied fixes.. It is categorised as a Read tool in the Ccboot MCP Server, which means it retrieves data without modifying state.
Register the Ccboot MCP server in PolicyLayer and add a rule for ccboot_validate_config: 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 Ccboot. Nothing to install.
ccboot_validate_config 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 ccboot_validate_config 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 ccboot_validate_config. 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.
ccboot_validate_config is provided by the Ccboot MCP server (ccboot-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 Ccboot tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.