Assign code blocks to the currently active intent. Call this AFTER writing code to track which lines were modified: 1. For each file you modified, provide the line range 2. Blocks get assigned to the active intent 3. This enables tracking, conflict detection, and team visibility Example: After ...
Part of the Kawa Code MCP MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use assign_blocks_to_intent to create or modify resources in Kawa Code MCP. 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 assign_blocks_to_intent 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 Kawa Code MCP.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
assign_blocks_to_intent:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Kawa Code MCP policy for all 17 tools.
Agents calling write-class tools like assign_blocks_to_intent 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.
Assign code blocks to the currently active intent. Call this AFTER writing code to track which lines were modified: 1. For each file you modified, provide the line range 2. Blocks get assigned to the active intent 3. This enables tracking, conflict detection, and team visibility Example: After adding a function at lines 50-75 in auth.ts, call with: { blocks: [{ filePath: "src/auth.ts", startLine: 50, endLine: 75 }] }. It is categorised as a Write tool in the Kawa Code MCP 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 assign_blocks_to_intent. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Kawa Code MCP MCP server.
assign_blocks_to_intent 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 assign_blocks_to_intent 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 assign_blocks_to_intent. 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.
assign_blocks_to_intent is provided by the Kawa Code MCP MCP server (@kawacode/mcp). 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