dials_createMessagingCampaign
Save a pending campaign for a verified owned brand (POST /v1/dials/messaging/campaigns) [service status: unverified]
This record as markdown: /tools/lifesi-genesis-mcp/dials-createmessagingcampaign.md
What dials_createMessagingCampaign does on Genesis
AI agents use dials_createMessagingCampaign to create or update resources in Genesis, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Genesis environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | object | Yes | Persist a pending campaign. The brand must exist in the same five-axis scope and already have status verified; otherwise 404 or422. Same scoped brand/name retur |
Parameters from the server's own tool schema.
Why dials_createMessagingCampaign is rated Medium
An AI agent can call dials_createMessagingCampaign faster than any human can review: one bad instruction and it creates or modifies resources in Genesis by the hundred, each call as confident as the last.
Risk signalsAccepts raw HTML/template content (body) · High parameter count (23 properties)
Attacks that exploit this kind of access
The rule that runs dials_createMessagingCampaign safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Genesis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dials_createMessagingCampaign, this is the rule to start with:
dials_createMessagingCampaign stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Genesis, apply this rule, and every dials_createMessagingCampaign call is checked against it from then on.
Questions about dials_createMessagingCampaign
Save a pending campaign for a verified owned brand (POST /v1/dials/messaging/campaigns) [service status: unverified]. It is categorised as a Write tool in the Genesis MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
dials_createMessagingCampaign accepts 1 parameter: body. Required: body. The full parameter table on this page comes from the server's own tool schema.
Register the Genesis MCP server in PolicyLayer and add a rule for dials_createMessagingCampaign: 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 Genesis. Nothing to install.
dials_createMessagingCampaign 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 dials_createMessagingCampaign 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 dials_createMessagingCampaign. 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.
dials_createMessagingCampaign is provided by the Genesis MCP server (@lifesi/genesis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Genesis, and thousands of servers like it.
This server
Across the catalogue