search_transactions
Search transactions by description. Use when user asks about specific vendors, expenses, or payments.
This record as markdown: /tools/com-getfreedomos-freedom-mcp/search-transactions.md
What search_transactions does on Freedom Mcp
AI agents call search_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 (default: 10) |
query | string | Yes | Text to search for in transaction descriptions |
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 search_transactions is rated Low
This tool retrieves or queries financial transaction data without creating, modifying, deleting, or executing external operations. It is a passive read operation that returns information about existing transactions. While it accesses financial data, it does not move money, commit obligations, or alter records—it only retrieves information.
From the tool's definition Tool name 'search_transactions' and description 'Search transactions by description' indicate a query operation.
Attacks that exploit this kind of access
The rule that runs search_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 search_transactions, this is the rule to start with:
search_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 search_transactions call is checked against it from then on.
Questions about search_transactions
Search transactions by description. Use when user asks about specific vendors, expenses, or payments. It is categorised as a Read tool in the Freedom Mcp MCP Server, which means it retrieves data without modifying state.
search_transactions accepts 3 parameters: limit, query, companyId. Required: query, 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 search_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.
search_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 search_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 search_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.
search_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