get_decision_ledger
THE tool for what the Freedom Engine has DECIDED for this company — the audit feed of every autonomous decision: what it auto-ran, what it teed up for your approval, and what it refused (e.g. faith/values content), each with the reason, the profit at play, the founder-attention cost, and how fres...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/get-decision-ledger.md
What get_decision_ledger does on Freedom Mcp
AI agents call get_decision_ledger to retrieve information from Freedom Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | How many recent decisions to return, newest first (default 25, max 100). |
routing | string | — | Optional filter: AUTO_RUN (the engine ran it autonomously), TEE_UP (held for your approval), or REFUSE_AND_SURFACE (refused — e.g. faith/values content the foun |
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
Parameters from the server's own tool schema.
Why get_decision_ledger is rated Low
This tool retrieves and queries historical decision logs without modifying, deleting, or executing actions. It provides visibility into past decisions and reasoning (reason, profit impact, attention cost, input freshness) but does not change state or trigger operations. The explicit purpose is auditing and cockpit visibility for human decision-makers, making it a pure Read operation with low risk.
From the tool's definition Tool description explicitly states it retrieves and displays decision history: 'THE tool for what the Freedom Engine has DECIDED', 'the audit feed of every autonomous decision', 'Use for what did the engine do today'.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs get_decision_ledger safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freedom Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_decision_ledger, this is the rule to start with:
get_decision_ledger 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 Freedom Mcp, apply this rule, and every get_decision_ledger call is checked against it from then on.
Questions about get_decision_ledger
THE tool for what the Freedom Engine has DECIDED for this company — the audit feed of every autonomous decision: what it auto-ran, what it teed up for your approval, and what it refused (e.g. faith/values content), each with the reason, the profit at play, the founder-attention cost, and how fresh the inputs were. Use for "what did the engine do today", "what did it auto-run", "why did it hold that tactic", "show me the decision ledger / cockpit". This is the only tool with the engine's decision history — get_command_center_items shows open cards to act on, not the decision audit trail. It is categorised as a Read tool in the Freedom Mcp MCP Server, which means it retrieves data without modifying state.
get_decision_ledger accepts 3 parameters: limit, routing, companyId. Required: companyId. The full parameter table on this page comes from the server's own tool schema.
Register the Freedom MCP server in PolicyLayer and add a rule for get_decision_ledger: 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 Freedom Mcp. Nothing to install.
get_decision_ledger 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 get_decision_ledger 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 get_decision_ledger. 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.
get_decision_ledger is provided by the Freedom MCP server (https://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freedom, and thousands of servers like it.
This server
Across the catalogue