AI agents use create_files 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.
This tool creates multiple files in batch, which is a reversible Write operation. It modifies the file system by adding new files, but does not execute code, delete irreversibly, or move money. The 'sandboxed command engine with human approval gates' mentioned in the server description suggests safeguards are in place.
From the tool's definition Tool name 'create_files' and description 'Batch variant of' (incomplete, but contextually referring to create_file). Sibling tool 'create_file' is listed alongside deletion and folder operations in a knowledge vault system.
Attacks that exploit this kind of access
Batch variant of. 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_files: 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_files 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_files 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_files. 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_files 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.
create_files is one line of Kontexta's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →