17 tools from the Kawa Code MCP MCP Server, categorised by risk level.
View the Kawa Code MCP policy →check_active_intent 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 th... detect_intent_conflicts Detect conflicts between your local decisions and team members' decisions.
Call this before committing to check for potential conflicts.
The tool... 2/5 get_intent_changes Get uncommitted changes in the repository along with the active intent info.
Use this tool before prompting the user about committing to show:
- T... get_intents_for_file Get all intents that have code blocks in this file.
Use this before modifying a file to:
- See what work is already in progress
- Identify potenti... 2/5 get_intents_for_lines Get intents covering a specific line range.
Use this before modifying specific lines to check for conflicts:
- Warns if the lines overlap with ano... get_project_decisions Get all decisions recorded for a project across all intents.
Use this to review the project's decision history:
- See what architectural decisions... get_relevant_context Find context relevant to a specific user request.
Use this when you need context that's specifically relevant to the current task,
rather than all... get_session_decisions Get all decisions recorded in the current session for an intent.
Use this before committing to review what decisions were captured during developm... infer_history Analyze git commit history to extract structured development knowledge (intents and decisions).
Runs the full pipeline automatically: infer → evol... list_team_intents List all intents from team members for this repository.
Use this to:
- See what your team is working on
- Check for potential overlapping work bef... record_decision Silently record a decision point during development.
Call this tool when you:
- Choose between multiple alternatives (type: fork)
- Try an approac... assign_blocks_to_intent 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,... 2/5 complete_intent Mark the active intent as completed and clear it.
Call this after a successful git commit to:
1. Update the intent status (committed/pushed/done/a... 2/5 create_and_activate_intent 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.... 2/5 edit_session_decision Edit or delete a decision in the current session.
Use this when reviewing decisions before commit:
- action: "update" - Modify the decision fields... 2/5 log_work Lightweight single-call tool to log completed work without the full intent lifecycle. Use for quick fixes, doc updates, config changes — any task w... 2/5 The Kawa Code MCP MCP server exposes 17 tools across 3 categories: Read, Write, Execute.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Kawa Code MCP server.
Kawa Code MCP tools are categorised as Read (11), Write (5), Execute (1). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept