get_release_ledger

SERVERFreedom Mcp SOURCEhttps://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp

Low RISK CLASS

Category Read

Parameters 61 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-getfreedomos-freedom-mcp/get-release-ledger.md

WHAT IT DOES

What get_release_ledger does on Freedom Mcp

AI agents call get_release_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 releases to return, newest first (default 50, max 200).
`since`	string	—	ISO timestamp lower bound — only releases at/after this time.
`channel`	string	—	Filter to one channel.
`companyId`	string	Yes	FreedomOS company id to act within (you must be a member). Required for company-scoped tools.
`piece_key`	string	—	Filter to one piece's releases (e.g. 'output:<pipeline_outputs.id>', 'idea:<content_ideas.id>', 'hub-letter:<slug>').
`released_by`	string	—	Filter by who released it: 'agent', 'human', or 'system'.

Parameters from the server's own tool schema.

RISK

Why get_release_ledger is rated Low

This tool retrieves and queries historical publication data from an immutable ledger written by the publish rail. It performs no side effects—no data creation, modification, deletion, or external execution. The blast radius of misuse is minimal: an agent could retrieve sensitive release timing or metadata, but cannot alter records or trigger actions. Categorized as Read with low severity.

From the tool's definition Tool description states it 'reads the cross-channel Release Ledger' and 'Returns rows plus a per-piece coverage summary'. The verbs are query/read operations: 'queryable truth', 'asks whether a piece released', 'wants a recent-releases feed'.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_release_ledger Allowed

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

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

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

FAQ

Questions about get_release_ledger

What does the get_release_ledger tool do? +

THE tool for "did this piece ship on this channel" — reads the cross-channel Release Ledger, the queryable truth for every confirmed send (x/linkedin/instagram/facebook/threads, hub letters, Beehiiv) written by the publish rail itself at send time. Use this instead of title-matching or a markdown tracking doc when a reconciler or operator asks whether a piece released, where it released, or wants a recent-releases feed. Returns rows plus a per-piece coverage summary (which channels a piece is KNOWN to have shipped on — never a speculative claim about what's missing). It is categorised as a Read tool in the Freedom Mcp MCP Server, which means it retrieves data without modifying state.

What parameters does get_release_ledger accept? +

get_release_ledger accepts 6 parameters: limit, since, channel, companyId, piece_key, released_by. Required: companyId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_release_ledger? +

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

What risk level is get_release_ledger? +

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

Can I rate-limit get_release_ledger? +

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

How do I block get_release_ledger completely? +

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

What MCP server provides get_release_ledger? +

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

KEEP EXPLORING

More on Freedom, and thousands of servers like it.

This server

All 238 Freedom tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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