Applies a compliance template pack to the project — generates hooks for audit logging, skills for compliance-aware code review, and CLAUDE.md sections with regulatory requirements. Supported standards: • hipaa: PHI handling, audit logging, encryption requirements, data classification • soc2: Acc...
Part of the Ccboot MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use ccboot_apply_compliance to create or modify resources in Ccboot. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call ccboot_apply_compliance repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Ccboot.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
ccboot_apply_compliance:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Ccboot policy for all 16 tools.
Agents calling write-class tools like ccboot_apply_compliance have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Applies a compliance template pack to the project — generates hooks for audit logging, skills for compliance-aware code review, and CLAUDE.md sections with regulatory requirements. Supported standards: • hipaa: PHI handling, audit logging, encryption requirements, data classification • soc2: Access controls, audit trails, change management, encryption • pci-dss: Card number blocking, tokenization requirements, OWASP checks • sox: Financial calculation review, audit trails, separation of duties Scope options: • full: Hooks + skills + CLAUDE.md section • hooks_only: Just audit/blocking hooks • skills_only: Just compliance review skills Examples: ccboot_apply_compliance({ project_path: '.', standard: 'hipaa', scope: 'full' }) ccboot_apply_compliance({ project_path: '.', standard: 'soc2', scope: 'hooks_only' }) Idempotent: Safe to run multiple times — won't duplicate hooks.. It is categorised as a Write tool in the Ccboot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for ccboot_apply_compliance. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Ccboot MCP server.
ccboot_apply_compliance is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the ccboot_apply_compliance rule in your Intercept 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 Intercept policy for ccboot_apply_compliance. 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_apply_compliance is provided by the Ccboot MCP server (ccboot-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept