set_decision_status

SERVERAdrata SOURCE@adrata/adrata-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adrata-adrata-mcp/set-decision-status.md

WHAT IT DOES

What set_decision_status does on Adrata

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

RISK

Why set_decision_status is rated Medium

An AI agent can call set_decision_status faster than any human can review: one bad instruction and it creates or modifies resources in Adrata by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs set_decision_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Adrata, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_decision_status, this is the rule to start with:

set_decision_status Rate-limited

set_decision_status 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": {
    "set_decision_status": {
      "limits": [
        {
          "counter": "set_decision_status_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Adrata, apply this rule, and every set_decision_status call is checked against it from then on.

FAQ

Questions about set_decision_status

What does the set_decision_status tool do? +

Move a decision through its lifecycle: proposed → discussing → decided, or to superseded / reversed (prefer record_decision with supersedesDecisionId for those — a reversal is a new decision). decided needs decidedOn (defaults to today) and records the caller as the decider. A decision with sourcePath is git-owned for status and the API answers 409 naming the file; change the file instead. When an app-born decision becomes decided, the response carries gitHalf: write the company/decisions/ file. The reason is recorded on the transition and doubles as the audit reason.${GOVERNED_NOTE}. It is categorised as a Write tool in the Adrata MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_decision_status? +

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

What risk level is set_decision_status? +

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

Can I rate-limit set_decision_status? +

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

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

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

KEEP EXPLORING

More on Adrata, and thousands of servers like it.

This server

All 395 Adrata tools →

Across the catalogue

emit_assumption_set on 0sec →set-prioity on Kanban MCP Server →team_manager_emit_decision on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →