AI agents use create_folder to create or update resources in Kontexta — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kontexta environment.
Creating folders is a reversible write operation with no side effects beyond directory structure. The tool is idempotent and cannot delete or overwrite existing data. Blast radius is minimal — folders can be easily deleted. This is classic Write category: creates data without irreversibility, code execution, or destructive potential.
From the tool's definition Tool name 'create_folder' and description 'Create a folder under a project root or the KB. Idempotent — creating an existing folder succeeds.' — explicitly creates new directories.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Create a folder under a project root or the KB. Idempotent — creating an existing folder succeeds. Nested paths like. It is categorised as a Write tool in the Kontexta MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kontexta 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 Kontexta. 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 Kontexta MCP server (safiyu/kontexta). 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 →