export_decisions

Export decisions to JSONL or Markdown. Read-only; no schema mutations. Use for audit, sharing with external tooling, or pre-LLM digestion. JSONL emits one decision per line with

SERVERTrace SOURCEnikolai-vysotskyi/trace-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nikolai-vysotskyi-trace-mcp/export-decisions.md

WHAT IT DOES

What export_decisions does on Trace

AI agents call export_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.

RISK

Why export_decisions is rated Low

The tool explicitly states it is read-only with no schema mutations. It exports existing decision data into JSONL or Markdown formats for audit or sharing purposes, making it a pure read/retrieval operation with minimal blast radius.

From the tool's definition Export decisions to JSONL or Markdown. Read-only; no schema mutations. Use for audit, sharing with external tooling, or pre-LLM digestion.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs export_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 export_decisions, this is the rule to start with:

export_decisions Allowed

export_decisions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "export_decisions": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about export_decisions

What does the export_decisions tool do? +

Export decisions to JSONL or Markdown. Read-only; no schema mutations. Use for audit, sharing with external tooling, or pre-LLM digestion. JSONL emits one decision per line with. It is categorised as a Read tool in the Trace MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on export_decisions? +

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

What risk level is export_decisions? +

export_decisions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit export_decisions? +

Yes. Add a rate_limit block to the export_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.

How do I block export_decisions completely? +

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

What MCP server provides export_decisions? +

export_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.

KEEP EXPLORING

More on Trace, and thousands of servers like it.

This server

All 191 Trace tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →