decision_accept · Musubix MCP: Risk & Policy

WHAT IT DOES

What decision_accept does on Musubix

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

WHY IT NEEDS A POLICY

Why decision_accept needs a policy

Accepting a proposed ADR (Architecture Decision Record) is a Write operation — it changes the state of a proposal from pending to accepted. This is reversible (an ADR could potentially be revised or rejected later), so it does not qualify as Destructive. The blast radius is medium since architectural decisions can have downstream implications, but the action itself is a status update/approval workflow step.

From the tool's definition Accept a proposed ADR

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

decision_accept Rate-limited

decision_accept 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": {
    "decision_accept": {
      "limits": [
        {
          "counter": "decision_accept_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 Musubix, so you can run agents against it safely.

FAQ

Questions about decision_accept

What does the decision_accept tool do? +

Accept a proposed ADR. It is categorised as a Write tool in the Musubix MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on decision_accept? +

Register the Musubix MCP server in PolicyLayer and add a rule for decision_accept: 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 Musubix. Nothing to install.

What risk level is decision_accept? +

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

Can I rate-limit decision_accept? +

Yes. Add a rate_limit block to the decision_accept 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 decision_accept completely? +

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

decision_accept is provided by the Musubix MCP server (@nahisaho/musubix-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.