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...
Part of the Kawa Code MCP server.
Free to start. No card required.
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.
{
"version": "1",
"default": "deny",
"tools": {
"check_active_intent": {}
}
}See the full Kawa Code MCP policy for all 21 tools.
These attack patterns abuse exactly the kind of access check_active_intent gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
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 Status semantics: - "active" — normal, in-progress. - "pending" — auto-finalized by the orphan-recovery sweeper or blocked at completion by conflicts. Pending is treated as live context for the repo: prompt the user to resume the work (activate_intent) or finalize it (complete_intent) before starting new unrelated work. Inspect "pendingReason" to tell the user WHY the intent went pending — "sweeper-auto-finalize" (24h idle) or "sweeper-blocked-conflicts" (decisions contradicted standards on the auto-finalize attempt).. It is categorised as a Read tool in the Kawa Code MCP MCP Server, which means it retrieves data without modifying state.
Register the Kawa Code MCP server in PolicyLayer and add a rule for check_active_intent: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Kawa Code MCP. Nothing to install.
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 PolicyLayer 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 PolicyLayer 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 server (kawacode-ai/kawa.mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 Kawa Code MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.