Sends a message to an existing conversation or any type with a conversation_id.
AI agents use create_conversation_message to create or update resources in Carbon Voice — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Carbon Voice environment.
This tool creates new messages within conversations, which is a reversible write operation. It does not execute code or trigger external side effects beyond message creation, does not delete data (Destructive), and does not move money (Financial).
From the tool's definition Tool description states 'Sends a message to an existing conversation', which is a create/write operation that modifies conversation state by adding new message content.
Documented attack patterns abuse exactly the kind of access create_conversation_message gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Carbon Voice, and nothing reaches the server without passing your rules. This is the rule we recommend for create_conversation_message:
{
"version": "1",
"default": "deny",
"tools": {
"create_conversation_message": {
"limits": [
{
"counter": "create_conversation_message_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_conversation_message 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.
Free to start. No card required.
Sends a message to an existing conversation or any type with a conversation_id. It is categorised as a Write tool in the Carbon Voice MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Carbon Voice MCP server in PolicyLayer and add a rule for create_conversation_message: 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 Carbon Voice. Nothing to install.
create_conversation_message 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_conversation_message 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_conversation_message. 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_conversation_message is provided by the Carbon Voice MCP server (phononx/cv-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Carbon Voice, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
28 Carbon Voice tools catalogued and risk-classified — across an index of 43,000+ MCP servers.