Edit or delete a decision in the current session. Use this when reviewing decisions before commit: - action: "update" - Modify the decision fields - action: "delete" - Remove the decision entirely Only ephemeral (in-flight) session decisions are editable. Once a decision is synced to Kawa Code, i...
Part of the Kawa Code MCP server.
Free to start. No card required.
AI agents use edit_session_decision 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 edit_session_decision 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": {
"edit_session_decision": {
"limits": [
{
"counter": "edit_session_decision_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 edit_session_decision 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.
Edit or delete a decision in the current session. Use this when reviewing decisions before commit: - action: "update" - Modify the decision fields - action: "delete" - Remove the decision entirely Only ephemeral (in-flight) session decisions are editable. Once a decision is synced to Kawa Code, it is immutable — refine it instead by recording a new decision with supersedes: [<id>]. This allows users to curate their decision history before it's persisted.. 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 edit_session_decision: 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.
edit_session_decision 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 edit_session_decision 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 edit_session_decision. 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.
edit_session_decision 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.