query_decisions
Query the decision knowledge graph. Filter by type, subproject, code symbol, file path, tag, or time — answers
This record as markdown: /tools/nikolai-vysotskyi-trace-mcp/query-decisions.md
What query_decisions does on Trace
AI agents call query_decisions to retrieve information from Trace without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why query_decisions is rated Low
Tool retrieves and filters decision metadata from a knowledge graph without modifying or executing any code.
From the tool's definition Query the decision knowledge graph. Filter by type, subproject, code symbol, file path, tag, or time
Attacks that exploit this kind of access
The rule that runs query_decisions 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 query_decisions, this is the rule to start with:
query_decisions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Trace, apply this rule, and every query_decisions call is checked against it from then on.
Questions about query_decisions
Query the decision knowledge graph. Filter by type, subproject, code symbol, file path, tag, or time — answers. It is categorised as a Read tool in the Trace MCP Server, which means it retrieves data without modifying state.
Register the Trace MCP server in PolicyLayer and add a rule for query_decisions: 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.
query_decisions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the query_decisions 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 query_decisions. 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.
query_decisions 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.
More on Trace, and thousands of servers like it.
This server
Across the catalogue