Add attachments to a message. In order to add attachments to a message, you must provide a message id and the attachments.
AI agents use add_attachments_to_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.
The tool modifies message data by adding attachments, making it a Write operation rather than Read (which would only retrieve data). It is not Destructive because attachments can typically be removed. It is not Execute because it doesn't run code or trigger external operations based on dynamic arguments—it simply attaches files to a message.
From the tool's definition Tool description states "Add attachments to a message" which modifies an existing message by appending attachments to it. This is a reversible modification operation.
Documented attack patterns abuse exactly the kind of access add_attachments_to_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 add_attachments_to_message:
{
"version": "1",
"default": "deny",
"tools": {
"add_attachments_to_message": {
"limits": [
{
"counter": "add_attachments_to_message_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} add_attachments_to_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.
Add attachments to a message. In order to add attachments to a message, you must provide a message id and the attachments. 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 add_attachments_to_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.
add_attachments_to_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 add_attachments_to_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 add_attachments_to_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.
add_attachments_to_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.