Check whether the line range about to be edited has prior recorded reasoning attached. Call this BEFORE editing code in a kawa-indexed repo. Surfaces: - Tier 1a — overlapping intents whose blocks cover these lines (line-precise team coordination + intent-scoped decisions) - Tier 1b — repo decisio...
Risk signalsAccepts file system path (filePath)
Part of the Kawa Code MCP server.
Free to start. No card required.
AI agents use pre_edit_decision_check 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 pre_edit_decision_check 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": {
"pre_edit_decision_check": {
"limits": [
{
"counter": "pre_edit_decision_check_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 pre_edit_decision_check 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.
Check whether the line range about to be edited has prior recorded reasoning attached. Call this BEFORE editing code in a kawa-indexed repo. Surfaces: - Tier 1a — overlapping intents whose blocks cover these lines (line-precise team coordination + intent-scoped decisions) - Tier 1b — repo decisions whose relatedFiles include this file (file-coarse, catches infer_history-extracted constraints) Decisions already overridden via record_decision(supersedes=...) are filtered out automatically. Recommendation maps to action: - "proceed" — nothing relevant; safe to edit - "review" — surfaced context worth inspecting before editing - "investigate-upstream" — prior constraint or abandoned approach matches; don't proceed without reading the rationale and either revising the change or recording a new fork decision that supersedes the old one Also returns the smallest enclosing function/method symbol via tree-sitter (Rust/TS/JS/Python only; null for other languages) for warning readability.. 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 pre_edit_decision_check: 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.
pre_edit_decision_check 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 pre_edit_decision_check 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 pre_edit_decision_check. 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.
pre_edit_decision_check 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.