18 tools from the Kai MCP Server, categorised by risk level.
View the Kai policy →kai_activity Show recent file changes detected by the live graph watcher. kai_blame Show AI vs human authorship for a file. Returns per-line attribution or a summary showing which agent/model authored each section. 2/5 kai_callees Find which symbols/files are called from a given symbol. kai_callers Find which files/functions call a given symbol. kai_checkpoint Record an AI code authorship checkpoint. Call this after editing files to track which code was AI-generated. Lightweight — writes a small JSON file... kai_context Get callers, callees, tests, and dependencies for a specific file. Use only when you need to understand call relationships before editing — not for... kai_dependencies Find files that a given file imports/depends on. kai_dependents Find files that import/depend on a given file. kai_impact Find all files and tests affected by changing a file, with hop distance. Use before making edits to assess blast radius — not for read-only explora... 2/5 kai_live_sync Enable or disable real-time sync with other agents. When on, you'll see other agents' changes as they happen via SSE. kai_stats Return project-wide authorship statistics. kai_symbols List symbols defined in a file with names, kinds, and line numbers. Use 'kind' to filter (e.g. only functions). Use 'exported=true' for Go public s... 2/5 kai_sync Fetch edge changes other agents have made since your last sync. Shows what files and relationships changed, who changed them, and when. kai_tests Find test files that cover a given source file. kai_lock Acquire advisory locks on files. Other agents will see the lock but can still edit (soft lock). Locks auto-expire after 5 minutes of inactivity. 2/5 kai_merge_check Check if your current changes can merge cleanly with other agents' work. Call before finalizing edits to catch conflicts early. 2/5 kai_unlock Release advisory locks on files. 2/5 The Kai MCP server exposes 18 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 Kai server.
Kai tools are categorised as Read (14), Write (3), Execute (1). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept