create_campaign
AI agents use create_campaign to create or update resources in VoIPbin MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your VoIPbin MCP Server environment.
The 'create_' prefix and sibling tools (create_call, create_flow, create_contact) establish a pattern of resource creation. Campaign creation in a VoIPbin context likely involves setting up outbound communications or marketing automation. This is Write rather than Execute because it creates a data entity rather than triggering arbitrary operations.
From the tool's definition Tool name 'create_campaign' indicates creation of a new resource. Description is empty, limiting confidence. Based on naming convention and VoIPbin context (CPaaS platform for calls, flows, messaging), this creates a campaign entity.
Attacks that exploit this kind of access
create_campaign. It is categorised as a Write tool in the VoIPbin MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the VoIPbin MCP Server MCP server in PolicyLayer and add a rule for create_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 VoIPbin MCP Server. Nothing to install.
create_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 create_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 create_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.
create_campaign is provided by the VoIPbin MCP Server MCP server (voipbin/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →