Reject a decision currently in the memoir-style review queue (review_status=
AI agents use reject_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.
Rejecting a decision in a review queue modifies the status and state of a decision record, making this a Write operation that reverses or changes a prior decision state. It is not destructive (the decision can be reactivated/re-reviewed) and not execute/financial in nature.
From the tool's definition Tool description states 'Reject a decision currently in the memoir-style review queue', indicating modification of decision/review state. The truncated description 'review_status=' suggests state change operation.
Documented attack patterns abuse exactly the kind of access reject_decision gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Trace, and nothing reaches the server without passing your rules. This is the rule we recommend for reject_decision:
{
"version": "1",
"default": "deny",
"tools": {
"reject_decision": {
"limits": [
{
"counter": "reject_decision_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}reject_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.
Free to start. No card required.
Reject 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.
Register the Trace MCP server in PolicyLayer and add a rule for reject_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.
reject_decision is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the reject_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.
Set action: deny in the PolicyLayer policy for reject_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.
reject_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.
Deterministic rules across all 178 Trace tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
178 Trace tools catalogued and risk-classified — across an index of 42,500+ MCP servers.