list_products
List shop products with optional filters by name, status, or category.
This record as markdown: /tools/io-favcrm-favcrm/list-products.md
What list_products does on FavCRM
AI agents call list_products 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 |
|---|---|---|---|
limit | number | — | Max results (default 20) |
search | string | — | Search by product name |
status | string | — | Filter by status |
categoryId | number | — | Filter by category ID |
Parameters from the server's own tool schema.
Why list_products is rated Low
This tool queries and retrieves product data from the CRM's shop. It performs no modifications, deletions, or external actions. The optional filtering parameters (name, status, category) are for scoping the query, not for mutating data. This is a straightforward Read operation with minimal risk—the blast radius of misuse is limited to exposure of product catalog information.
From the tool's definition Tool name 'list_products' and description 'List shop products with optional filters by name, status, or category' indicate a retrieval operation with no side effects. The verb 'list' combined with 'optional filters' is characteristic of a Read operation.
Attacks that exploit this kind of access
The rule that runs list_products 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_products, this is the rule to start with:
list_products 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_products call is checked against it from then on.
Questions about list_products
List shop products with optional filters by name, status, or category. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.
list_products accepts 4 parameters: limit, search, status, categoryId. 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_products: 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_products 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_products 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_products. 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_products 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