list_deals
List CRM deals for the current company. Filter by stage and limit. Returns deals with their associated contacts. Routing: CRM/sales → see open pipeline → use this
This record as markdown: /tools/com-getfreedomos-freedom-mcp/list-deals.md
What list_deals does on Freedom Mcp
AI agents call list_deals 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 number of deals to return (default 20, max 100) |
stage | string | — | Filter by stage (optional) |
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
include_closed | boolean | — | Include closed deals (default false) |
Parameters from the server's own tool schema.
Why list_deals is rated Low
This tool retrieves and queries existing CRM deal data filtered by stage and limit parameters. It has no side effects: it does not create, modify, delete, or execute any operations. The routing context ('see open pipeline') confirms it is a read-only view into sales pipeline data. No financial transactions are triggered, no code is executed, and no data is altered.
From the tool's definition Tool name is 'list_deals' and description states it 'List CRM deals' and 'Returns deals with their associated contacts' — pure data retrieval with no modification, deletion, or execution.
Attacks that exploit this kind of access
The rule that runs list_deals 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 list_deals, this is the rule to start with:
list_deals 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 list_deals call is checked against it from then on.
Questions about list_deals
List CRM deals for the current company. Filter by stage and limit. Returns deals with their associated contacts. Routing: CRM/sales → see open pipeline → use this. It is categorised as a Read tool in the Freedom Mcp MCP Server, which means it retrieves data without modifying state.
list_deals accepts 4 parameters: limit, stage, companyId, include_closed. 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 list_deals: 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.
list_deals 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 list_deals 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 list_deals. 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.
list_deals 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