file.create · Freedcamp MCP Server MCP: Risk & Policy

WHAT IT DOES

What file.create does on Freedcamp MCP Server

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

WHY IT NEEDS A POLICY

Why file.create needs a policy

This tool creates and persists new file objects within the Freedcamp project management system. It is reversible (files can be deleted), so it does not qualify as Destructive. It does not execute arbitrary code or shell commands (Execute), move money (Financial), or read/query data without modification (Read). Write is the appropriate category for this file creation operation.

From the tool's definition Tool description states "Upload and attach a file" which creates new file resources in the Freedcamp system. The use of "multipart/form-data" and requirement for project_id/group_id and item_id parameters indicates file creation/attachment operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

file.create Rate-limited

file.create 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": {
    "file.create": {
      "limits": [
        {
          "counter": "file.create_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 Freedcamp MCP Server, so you can run agents against it safely.

FAQ

Questions about file.create

What does the file.create tool do? +

Upload and attach a file using multipart/form-data. Provide file_path plus data fields such as project_id/group_id, application_id, and item_id. It is categorised as a Write tool in the Freedcamp MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on file.create? +

Register the Freedcamp MCP Server MCP server in PolicyLayer and add a rule for file.create: 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 Freedcamp MCP Server. Nothing to install.

What risk level is file.create? +

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

Can I rate-limit file.create? +

Yes. Add a rate_limit block to the file.create 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 file.create completely? +

Set action: deny in the PolicyLayer policy for file.create. 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 file.create? +

file.create is provided by the Freedcamp MCP Server MCP server (mahrukh-n8n/freedcampmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.