Send a Direct Message (DM) to a User or a Group of Users.
AI agents use create_direct_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 (write operation), which is reversible through deletion. It does not execute code, delete data irreversibly, or involve financial transactions. The severity is medium rather than low because sending unsolicited or malicious messages via an agent could constitute harassment, spam, or social engineering attacks if the agent were compromised or misdirected.
From the tool's definition The tool description explicitly states 'Send a Direct Message (DM) to a User or a Group of Users.' The verb 'send' combined with the ability to compose and deliver messages to other users indicates this is a write operation that creates new data (messages) in…
Documented attack patterns abuse exactly the kind of access create_direct_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_direct_message:
{
"version": "1",
"default": "deny",
"tools": {
"create_direct_message": {
"limits": [
{
"counter": "create_direct_message_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_direct_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.
Send a Direct Message (DM) to a User or a Group of Users. 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_direct_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_direct_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_direct_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_direct_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_direct_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.