Send a personalized cold-outreach email campaign for an offer the agent has accepted. Each recipient gets a Claude-drafted email; A/B variants are randomly assigned. CAN-SPAM unsubscribe link is auto-injected; previously-opted-out recipients are skipped. Outcome events stream back via the offer's...
Risk signalsHigh parameter count (11 properties)
Part of the Computeback server.
Free to start. No card required.
AI agents use dispatch_email_campaign to create or modify resources in Computeback. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call dispatch_email_campaign repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Computeback.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"dispatch_email_campaign": {
"limits": [
{
"counter": "dispatch_email_campaign_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Computeback policy for all 28 tools.
These attack patterns abuse exactly the kind of access dispatch_email_campaign gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Send a personalized cold-outreach email campaign for an offer the agent has accepted. Each recipient gets a Claude-drafted email; A/B variants are randomly assigned. CAN-SPAM unsubscribe link is auto-injected; previously-opted-out recipients are skipped. Outcome events stream back via the offer's webhook configuration.. It is categorised as a Write tool in the Computeback MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Computeback MCP server in PolicyLayer and add a rule for dispatch_email_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 Computeback. Nothing to install.
dispatch_email_campaign is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the dispatch_email_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 dispatch_email_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.
dispatch_email_campaign is provided by the Computeback MCP server (@autonomad1/computeback-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 28 Computeback tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.