upload_import_file
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.
This record as markdown: /tools/sankahq-sanka-mcp/upload-import-file.md
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 upload_import_file is rated Medium
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
The rule that runs upload_import_file safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sanka MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For upload_import_file, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Sanka MCP Server, apply this rule, and every upload_import_file call is checked against it from then on.
Questions about upload_import_file
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.
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.
upload_import_file 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 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.
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.
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.
More on Sanka MCP Server, and thousands of servers like it.
This server
Across the catalogue