AI agents use create_folder 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.
Creating a folder is a reversible write operation—folders can be deleted (as evidenced by the sibling 'delete_folder' tool). It does not read data, execute arbitrary code, destroy existing data, nor involve financial transactions. The low severity reflects minimal blast radius: a misused folder creation would clutter the user's workspace but cause no data loss or security breach.
From the tool's definition Tool name 'create_folder' and description 'Create a new folder' indicate irreversible creation of a new organizational container within the Carbon Voice system. This is a write operation that modifies the user's folder structure.
Documented attack patterns abuse exactly the kind of access create_folder 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_folder:
{
"version": "1",
"default": "deny",
"tools": {
"create_folder": {
"limits": [
{
"counter": "create_folder_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_folder 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.
Create a new folder. 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_folder: 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_folder 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_folder 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_folder. 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_folder 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.