Create a new folder in a FuseBase workspace. Optionally specify a parentId to create a subfolder. Returns the created folder
AI agents use create_folder to create or update resources in Fusebase MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fusebase MCP Server environment.
This tool creates a new folder in a workspace, which is a reversible Write operation. Creating a folder has minimal blast radius—it does not delete data, execute code, move funds, or trigger external operations. The impact is confined to workspace organization and can be undone by deleting the folder.
From the tool's definition Tool name 'create_folder' and description 'Create a new folder' indicate data creation. Returns 'the created folder', confirming a reversible write operation.
Attacks that exploit this kind of access
Create a new folder in a FuseBase workspace. Optionally specify a parentId to create a subfolder. Returns the created folder. It is categorised as a Write tool in the Fusebase MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fusebase MCP Server 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 Fusebase MCP Server. 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 Fusebase MCP Server MCP server (ryan-haver/fusebase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →