list_service_packages
List service packages/prepaid session bundles with optional search, status, sorting, and pagination.
This record as markdown: /tools/io-favcrm-favcrm/list-service-packages.md
What list_service_packages does on FavCRM
AI agents call list_service_packages 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 |
|---|---|---|---|
sort | string | — | Sort column: name, price, or createdAt |
limit | number | — | Max results (default 20) |
order | string | — | Sort order |
search | string | — | Search package name |
status | string | — | Filter by package status |
Parameters from the server's own tool schema.
Why list_service_packages is rated Low
This tool retrieves and queries service package data without any side effects. It provides filtering and pagination but does not create, modify, delete, or execute any operations. It is a straightforward data retrieval function typical of CRM list endpoints.
From the tool's definition Tool name is 'list_service_packages' and description states it 'List[s] service packages' with 'search, status, sorting, and pagination' — all read-only query operations with no modification, deletion, or execution of external commands.
Attacks that exploit this kind of access
The rule that runs list_service_packages 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_service_packages, this is the rule to start with:
list_service_packages 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_service_packages call is checked against it from then on.
Questions about list_service_packages
List service packages/prepaid session bundles with optional search, status, sorting, and pagination. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.
list_service_packages accepts 5 parameters: sort, limit, order, search, 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_service_packages: 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_service_packages 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_service_packages 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_service_packages. 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_service_packages 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