validate_campaign
Validate a campaign before sending. Resolves contactable recipient count and previews the final email subject/body without sending.
This record as markdown: /tools/io-favcrm-favcrm/validate-campaign.md
What validate_campaign does on FavCRM
AI agents call validate_campaign 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 |
|---|---|---|---|
campaignId | string | Yes | Campaign ID to validate |
Parameters from the server's own tool schema.
Why validate_campaign is rated Low
This tool performs validation and preview operations only. It queries data (recipient count, email preview) to help users verify campaign configuration before execution. No data is modified, deleted, or sent. It is purely informational with no side effects, fitting the Read category. The low severity reflects that misuse would only expose preview information, not cause harm.
From the tool's definition Tool description states it 'Resolves contactable recipient count and previews the final email subject/body without sending.' The explicit mention of 'without sending' and 'previews' indicates no actual campaign is executed or modified.
Attacks that exploit this kind of access
The rule that runs validate_campaign 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 validate_campaign, this is the rule to start with:
validate_campaign 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 validate_campaign call is checked against it from then on.
Questions about validate_campaign
Validate a campaign before sending. Resolves contactable recipient count and previews the final email subject/body without sending. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.
validate_campaign accepts 1 parameter: campaignId. Required: campaignId. 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 validate_campaign: 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.
validate_campaign 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 validate_campaign 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 validate_campaign. 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.
validate_campaign 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