get_transactions
List company transactions with optional filters. Use for expense tracking, transaction review.
This record as markdown: /tools/com-getfreedomos-freedom-mcp/get-transactions.md
What get_transactions does on Freedom Mcp
AI agents call get_transactions 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 | — | Max results to return (default: 25, max: 100) |
status | string | — | Filter by status |
date_to | string | — | End date filter (ISO format) |
category | string | — | Filter by category |
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
date_from | string | — | Start date filter (ISO format, e.g., 2026-01-01) |
is_income | boolean | — | Filter to income (true) or expenses (false) |
Parameters from the server's own tool schema.
Why get_transactions is rated Low
This tool retrieves or lists existing transaction data. It does not create, modify, delete, or execute any financial movements. While it accesses financial information (which could be sensitive), the action is read-only with no side effects or ability to commit financial obligations. Classification as Read is appropriate with low severity since it merely exposes visibility into existing transactions.
From the tool's definition Tool name 'get_transactions' and description 'List company transactions with optional filters. Use for expense tracking, transaction review' indicate retrieval and querying of financial data without modification, deletion, or execution of payments.
Attacks that exploit this kind of access
The rule that runs get_transactions 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_transactions, this is the rule to start with:
get_transactions 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_transactions call is checked against it from then on.
Questions about get_transactions
List company transactions with optional filters. Use for expense tracking, transaction review. It is categorised as a Read tool in the Freedom Mcp MCP Server, which means it retrieves data without modifying state.
get_transactions accepts 7 parameters: limit, status, date_to, category, companyId, date_from, is_income. 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_transactions: 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_transactions 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_transactions 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_transactions. 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_transactions 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