approve_decision

Approve a decision currently in the memoir-style review queue (review_status=

SERVERTrace SOURCEnikolai-vysotskyi/trace-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/nikolai-vysotskyi-trace-mcp/approve-decision.md

WHAT IT DOES

What approve_decision does on Trace

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

RISK

Why approve_decision is rated Medium

The tool approves (transitions state of) decisions in a review queue. This is a state modification action that persists changes to decision records, fitting the Write category (reversible modification).

From the tool's definition 'Approve a decision currently in the memoir-style review queue' — this modifies the review_status of a decision, changing it from pending to approved state. It creates or updates metadata about code decisions.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs approve_decision safely

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

approve_decision Rate-limited

approve_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": {
    "approve_decision": {
      "limits": [
        {
          "counter": "approve_decision_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 Trace, apply this rule, and every approve_decision call is checked against it from then on.

FAQ

Questions about approve_decision

What does the approve_decision tool do? +

Approve a decision currently in the memoir-style review queue (review_status=. It is categorised as a Write tool in the Trace MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on approve_decision? +

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

What risk level is approve_decision? +

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

Can I rate-limit approve_decision? +

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

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

approve_decision is provided by the Trace MCP server (nikolai-vysotskyi/trace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Trace, and thousands of servers like it.

This server

All 191 Trace tools →

Across the catalogue

team_manager_emit_decision on Team Manager MCP → The MCP Attack Database →

Guides

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