Medium Risk

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 - action: "delete" - Remove the decision entirely This allows users to curate their decision history before it's persisted.

Part of the Kawa Code MCP MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@kawacode/mcp Write Risk 2/5

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. Intercept'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.

kawa-code-mcp.yaml
tools:
  edit_session_decision:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Kawa Code MCP policy for all 17 tools.

Tool Name edit_session_decision
Category Write
Risk Level Medium

View all 17 tools →

Agents calling write-class tools like edit_session_decision have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the edit_session_decision tool do? +

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 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.

How do I enforce a policy on edit_session_decision? +

Add a rule in your Intercept YAML policy under the tools section for edit_session_decision. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Kawa Code MCP MCP server.

What risk level is edit_session_decision? +

edit_session_decision is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit edit_session_decision? +

Yes. Add a rate_limit block to the edit_session_decision rule in your Intercept 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.

How do I block edit_session_decision completely? +

Set action: deny in the Intercept 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.

What MCP server provides edit_session_decision? +

edit_session_decision is provided by the Kawa Code MCP MCP server (@kawacode/mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Kawa Code MCP

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.