update_architecture_decision · Claude Session Continuity MCP

WHAT IT DOES

What update_architecture_decision does on Claude Session Continuity

AI agents use update_architecture_decision to create or update resources in Claude Session Continuity — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Session Continuity environment.

WHY IT NEEDS A POLICY

Why update_architecture_decision needs a policy

This tool creates or modifies project metadata (architecture decisions) in a reversible manner. It does not execute code, delete data irreversibly, or move financial resources. The medium severity reflects that misuse could corrupt project documentation or add misleading architectural constraints, affecting team decision-making, but the impact is limited to metadata and can typically be corrected.

From the tool's definition Tool name is 'update_architecture_decision' and description states '프로젝트에 아키텍처 결정을 추가합니다' (adds architecture decisions to the project). The verb 'update' and 'add' indicate data creation/modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_architecture_decision Rate-limited

update_architecture_decision stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_architecture_decision": {
      "limits": [
        {
          "counter": "update_architecture_decision_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Claude Session Continuity, so you can run agents against it safely.

FAQ

Questions about update_architecture_decision

What does the update_architecture_decision tool do? +

프로젝트에 아키텍처 결정을 추가합니다. 중요한 기술 결정 시 호출. It is categorised as a Write tool in the Claude Session Continuity MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_architecture_decision? +

Register the Claude Session Continuity MCP server in PolicyLayer and add a rule for update_architecture_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 Claude Session Continuity. Nothing to install.

What risk level is update_architecture_decision? +

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

Can I rate-limit update_architecture_decision? +

Yes. Add a rate_limit block to the update_architecture_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.

How do I block update_architecture_decision completely? +

Set action: deny in the PolicyLayer policy for update_architecture_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 update_architecture_decision? +

update_architecture_decision is provided by the Claude Session Continuity MCP server (leesgit/claude-session-continuity-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.