Mark a decision as no longer valid. The decision remains in the knowledge graph for historical queries but is excluded from active queries. Use when a decision is superseded or reversed. Mutates the decision store; idempotent. Returns JSON: { invalidated: { id, title, valid_until } }.
AI agents use invalidate_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.
This tool modifies the state of a decision record by marking it invalid, but explicitly preserves the record for historical queries. It is a reversible state change (soft invalidation, not deletion), making it Write rather than Destructive. Misuse could corrupt the active decision graph, warranting medium severity.
From the tool's definition Mark a decision as no longer valid... Mutates the decision store; idempotent. Returns JSON: { invalidated: { id, title, valid_until } }
Documented attack patterns abuse exactly the kind of access invalidate_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 invalidate_decision:
{
"version": "1",
"default": "deny",
"tools": {
"invalidate_decision": {
"limits": [
{
"counter": "invalidate_decision_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}invalidate_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.
Mark a decision as no longer valid. The decision remains in the knowledge graph for historical queries but is excluded from active queries. Use when a decision is superseded or reversed. Mutates the decision store; idempotent. Returns JSON: { invalidated: { id, title, valid_until } }. 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 invalidate_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.
invalidate_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 invalidate_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 invalidate_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.
invalidate_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.