get_decision_timeline

Chronological timeline of decisions for a project, symbol, or file. Shows when decisions were made and invalidated — like git log but for architectural decisions. Read-only. Use to review decision history. Returns JSON: { timeline: [{ id, title, type, created_at, valid_until }], count }.

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/get-decision-timeline.md

WHAT IT DOES

What get_decision_timeline does on Trace

AI agents call get_decision_timeline 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 get_decision_timeline is rated Low

This tool retrieves and queries architectural decision history with no side effects. It does not create, modify, delete, or execute anything — pure data retrieval matching the Read category profile.

From the tool's definition 'Chronological timeline of decisions for a project, symbol, or file' — retrieves historical decision data. 'Read-only' explicitly stated. Returns JSON timeline without modifying anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_decision_timeline Allowed

get_decision_timeline 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": {
    "get_decision_timeline": {}
  }
}

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 get_decision_timeline call is checked against it from then on.

FAQ

Questions about get_decision_timeline

What does the get_decision_timeline tool do? +

How do I enforce a policy on get_decision_timeline? +

Register the Trace MCP server in PolicyLayer and add a rule for get_decision_timeline: 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 get_decision_timeline? +

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

Can I rate-limit get_decision_timeline? +

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

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

get_decision_timeline 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

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