AI agents use update_folder_name 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.
Updating a folder name is a reversible write operation that modifies organizational metadata without affecting the underlying content, permissions, or financial impact. The blast radius is minimal—a user can undo or correct the change easily. This clearly falls under Write rather than Execute, Destructive, or other categories.
From the tool's definition Tool description states 'Update a folder name by its ID.' The word 'Update' indicates a reversible modification operation. This is a metadata change to a folder, not data deletion or destructive action.
Documented attack patterns abuse exactly the kind of access update_folder_name 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 update_folder_name:
{
"version": "1",
"default": "deny",
"tools": {
"update_folder_name": {
"limits": [
{
"counter": "update_folder_name_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} update_folder_name 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.
Update a folder name by its 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 update_folder_name: 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.
update_folder_name 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 update_folder_name 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 update_folder_name. 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.
update_folder_name 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.