REQUIRED: Call this tool BEFORE writing any code. Returns the currently active intent if one exists. If no active intent is set, you should ask the user to confirm intent details and then call create_and_activate_intent. An active intent tracks what the user is working on, enabling: - Better co...
Part of the Kawa Code MCP MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call check_active_intent to retrieve information from Kawa Code MCP 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 check_active_intent 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.
tools:
check_active_intent:
rules:
- action: allowSee the full Kawa Code MCP policy for all 17 tools.
Agents calling read-class tools like check_active_intent have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
REQUIRED: Call this tool BEFORE writing any code. Returns the currently active intent if one exists. If no active intent is set, you should ask the user to confirm intent details and then call create_and_activate_intent. An active intent tracks what the user is working on, enabling: - Better code context for AI-generated changes - Conflict detection with team members - Automatic assignment of code blocks to the intent. It is categorised as a Read tool in the Kawa Code MCP MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for check_active_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.
check_active_intent 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 check_active_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 check_active_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.
check_active_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