Activate an existing intent by ID without creating a new one. Use this to: - Switch to a different intent found via list_team_intents or get_relevant_context - Re-activate an intent that was deactivated (e.g., to complete it) - Resume work on a previously created intent - Resume an "abandoned" or...
Part of the Kawa Code MCP server.
Free to start. No card required.
AI agents use 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 activate_intent repeatedly, creating or modifying resources faster than any human could review. PolicyLayer'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.
{
"version": "1",
"default": "deny",
"tools": {
"activate_intent": {
"limits": [
{
"counter": "activate_intent_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Kawa Code MCP policy for all 21 tools.
These attack patterns abuse exactly the kind of access activate_intent gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Activate an existing intent by ID without creating a new one. Use this to: - Switch to a different intent found via list_team_intents or get_relevant_context - Re-activate an intent that was deactivated (e.g., to complete it) - Resume work on a previously created intent - Resume an "abandoned" or "pending" intent (see below) Accepts both cloud IDs (from get_relevant_context / API) and local UUIDs (from list_team_intents). Resuming abandoned / pending intents: - Abandoned intents have their decisions soft-deleted (invisible to recall and get_relevant_context). Activating one transparently restores them — single-intent decisions for this intent get their soft-delete cleared so the prior reasoning becomes visible again. Multi-intent decisions stay visible throughout (they were never soft-deleted). - Pending intents are intents auto-finalized by the orphan-recovery sweeper (24h inactivity) — possibly with conflicts blocking the finalization. Their decisions were never soft-deleted, so activating one is a clean resume; new ephemerals accumulate in a fresh bucket and the next complete_intent distills only the new work. Per-repo active-intent lock: if another session already has a different intent active on this repo, the tool returns action="conflict" with lockConflict details. Present the conflict to the user and choose one of: - Take over: retry with force=true (displaces the other session's active intent). - Complete first: call complete_intent on the existing intent, then retry. - Cancel: choose a different intent or stop.. 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.
Register the Kawa Code MCP server in PolicyLayer and add a rule for activate_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.
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 activate_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 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.
activate_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.