list_campaigns
List marketing campaigns (email, SMS, WhatsApp) with delivery stats.
This record as markdown: /tools/io-favcrm-favcrm/list-campaigns.md
What list_campaigns does on FavCRM
AI agents call list_campaigns 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 |
limit | number | — | Max results (default 20) |
order | string | — | Sort order |
search | string | — | Search by campaign name |
channel | string | — | Filter by channel |
Parameters from the server's own tool schema.
Why list_campaigns is rated Low
This tool retrieves and displays information about existing campaigns and their statistics. It does not create, modify, delete, or execute any actions—it simply lists data. This is a classic Read operation with minimal risk, as it only exposes campaign metadata and delivery metrics without enabling any changes or external operations.
From the tool's definition Tool name 'list_campaigns' and description 'List marketing campaigns... with delivery stats' indicate a query/retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_campaigns 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_campaigns, this is the rule to start with:
list_campaigns 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_campaigns call is checked against it from then on.
Questions about list_campaigns
List marketing campaigns (email, SMS, WhatsApp) with delivery stats. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.
list_campaigns accepts 5 parameters: sort, limit, order, search, channel. 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_campaigns: 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_campaigns 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_campaigns 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_campaigns. 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_campaigns 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