create_files · Vigentic MCP: Risk & Policy

WHAT IT DOES

What create_files does on Vigentic MCP

AI agents use create_files to create or update resources in Vigentic MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vigentic MCP environment.

WHY IT NEEDS A POLICY

Why create_files needs a policy

This tool creates or modifies files, which is a Write operation (reversible data modification). It is not Destructive because overwriting can be undone via version control or backups, and the tool does not permanently delete data.

From the tool's definition Tool description states 'Create or overwrite multiple files' - these are write operations that modify the filesystem by creating new files or overwriting existing ones. The 'overwrite' capability indicates reversible modification of file contents.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_files Rate-limited

create_files 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_files": {
      "limits": [
        {
          "counter": "create_files_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Vigentic MCP, so you can run agents against it safely.

FAQ

Questions about create_files

What does the create_files tool do? +

Create or overwrite multiple files in order. Parent directories must already exist for every entry unless createParents=true. It is categorised as a Write tool in the Vigentic MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_files? +

Register the Vigentic 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 Vigentic MCP. Nothing to install.

What risk level is create_files? +

create_files is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_files? +

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.

How do I block create_files completely? +

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.

What MCP server provides create_files? +

create_files is provided by the Vigentic MCP server (munozu/vigentic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.