list_deals
List CRM deals (sales pipeline) with optional filters.
This record as markdown: /tools/io-favcrm-favcrm/list-deals.md
What list_deals does on FavCRM
AI agents call list_deals to retrieve information from FavCRM 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 |
|---|---|---|---|
page | number | — | Page number (default 1) |
limit | number | — | Items per page (default 20) |
stage | string | — | Filter by stage |
search | string | — | Search by name or description |
dealType | string | — | Filter by deal type |
accountId | string | — | Filter by account |
Parameters from the server's own tool schema.
Why list_deals is rated Low
This tool retrieves or queries deal records from a sales pipeline with optional filtering. It performs no side effects, creates no data, executes no operations, and deletes nothing. This is a standard read/query operation typical of CRM data retrieval, representing minimal risk if misused by an AI agent.
From the tool's definition Tool is named 'list_deals' with description 'List CRM deals (sales pipeline) with optional filters' — uses 'list' verb and explicitly queries data without modifying it.
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 FavCRM, 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 FavCRM, apply this rule, and every list_deals call is checked against it from then on.
Questions about list_deals
List CRM deals (sales pipeline) with optional filters. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.
list_deals accepts 6 parameters: page, limit, stage, search, dealType, accountId. The full parameter table on this page comes from the server's own tool schema.
Register the FavCRM 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 FavCRM. 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 FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FavCRM, and thousands of servers like it.
This server
Across the catalogue