list_offer_rules
List upsell/cross-sell offer rules with optional filters.
This record as markdown: /tools/io-favcrm-favcrm/list-offer-rules.md
What list_offer_rules does on FavCRM
AI agents call list_offer_rules 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 |
|---|---|---|---|
type | string | — | Filter by rule type |
limit | number | — | Max results (default 20) |
status | string | — | Filter by status |
Parameters from the server's own tool schema.
Why list_offer_rules is rated Low
This tool retrieves and queries existing offer rule configurations. It performs a read-only operation that returns data without creating, modifying, deleting, or executing any changes. The presence of 'optional filters' confirms it is a query/retrieval operation. No reversible modifications, irreversible deletions, code execution, or financial transactions occur.
From the tool's definition Tool name contains 'list' and description states 'List upsell/cross-sell offer rules with optional filters.' The verb 'list' and the action of querying/retrieving existing offer rules with filters indicates data retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs list_offer_rules 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_offer_rules, this is the rule to start with:
list_offer_rules 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_offer_rules call is checked against it from then on.
Questions about list_offer_rules
List upsell/cross-sell offer rules with optional filters. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.
list_offer_rules accepts 3 parameters: type, limit, status. 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_offer_rules: 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_offer_rules 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_offer_rules 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_offer_rules. 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_offer_rules 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