upload_import_file · Sanka MCP Server MCP: Risk & Policy

WHAT IT DOES

What upload_import_file does on Sanka MCP Server

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

WHY IT NEEDS A POLICY

Why upload_import_file needs a policy

This tool creates new file data and establishes the first step in a data import pipeline. It is Write rather than Execute because the file upload itself does not directly trigger data import or external operations—that responsibility is delegated to import_records. It is not Destructive because the file is temporary and reversible.

From the tool's definition The tool uploads and creates a new file (temporary file_id) as part of an import flow. The description states 'Upload a CSV file' and 'return a temporary file_id', indicating creation of new data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

upload_import_file Rate-limited

upload_import_file 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": {
    "upload_import_file": {
      "limits": [
        {
          "counter": "upload_import_file_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 Sanka MCP Server, so you can run agents against it safely.

FAQ

Questions about upload_import_file

What does the upload_import_file tool do? +

Upload a CSV file for a public import flow and return a temporary file_id. Provide a filename and base64-encoded file content, then pass the returned file_id to import_records. It is categorised as a Write tool in the Sanka 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 upload_import_file? +

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

What risk level is upload_import_file? +

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

Can I rate-limit upload_import_file? +

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

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

upload_import_file is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.