Create a new intent from the user's request and mark it as active. Call this when check_active_intent returns no active intent. Before calling: 1. Summarize what the user is asking for 2. Ask the user to confirm the intent details (title, description, type) 3. Then call this tool with the confir...
Part of the Kawa Code MCP MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use create_and_activate_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 create_and_activate_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:
create_and_activate_intent:
rules:
- action: allow
rate_limit:
max: 30
window: 60 See the full Kawa Code MCP policy for all 17 tools.
Agents calling write-class tools like create_and_activate_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.
Create a new intent from the user's request and mark it as active. Call this when check_active_intent returns no active intent. Before calling: 1. Summarize what the user is asking for 2. Ask the user to confirm the intent details (title, description, type) 3. Then call this tool with the confirmed details This ensures all AI-generated code gets properly tracked and attributed.. 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 create_and_activate_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.
create_and_activate_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 create_and_activate_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 create_and_activate_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.
create_and_activate_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