Creates a slash command (e.g., /review, /deploy, /docs) as a skill with user invocation. Slash commands are the primary way teams standardize Claude Code workflows. When a user types /command-name, Claude receives the prompt_body as instructions. Examples: ccboot_create_command({ name: "revie...
Part of the Ccboot MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use ccboot_create_command 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_create_command 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_create_command:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Ccboot policy for all 16 tools.
Agents calling write-class tools like ccboot_create_command 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.
Creates a slash command (e.g., /review, /deploy, /docs) as a skill with user invocation. Slash commands are the primary way teams standardize Claude Code workflows. When a user types /command-name, Claude receives the prompt_body as instructions. Examples: ccboot_create_command({ name: "review", description: "Review current changes", prompt_body: "Review the current git diff. Check for security issues, performance problems, and code quality. Output findings as Critical/Warning/Suggestion." }) ccboot_create_command({ name: "deploy-check", description: "Pre-deploy checklist", prompt_body: "Run through the deployment checklist: 1. All tests pass 2. No TODO/FIXME in changed files 3. No console.log statements 4. Database migrations are reversible", arguments: [{ name: "env", description: "Target environment", required: true }] }) Returns: Slash command usage, file location. Error: If command name already exists.. 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_create_command. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Ccboot MCP server.
ccboot_create_command 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_create_command 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_create_command. 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_create_command 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