upload_data
Upload or replace a data file (CSV, JSON, TSV, XML, TXT, max 10MB) inside an already-deployed Deloc app WITHOUT redeploying. Use this to refresh dashboard data from databases or APIs on a schedule. The file is served at the same URL as the rest of the app, so client code that does fetch(
This record as markdown: /tools/deloc-mcp/upload-data.md
What upload_data does on Deloc
AI agents use upload_data to create or update resources in Deloc, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Deloc environment.
Why upload_data is rated Medium
This tool creates or modifies data files reversibly—uploading or replacing CSV, JSON, TSV, XML, or TXT files up to 10MB in size within an already-deployed app. While this can affect the app's behavior (since the file is served via fetch), it doesn't execute arbitrary code, delete data irreversibly, or trigger financial transactions.
From the tool's definition Tool description states 'Upload or replace a data file' and mentions refreshing data, which are write operations that modify existing files without permanent deletion or code execution.
Attacks that exploit this kind of access
The rule that runs upload_data safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Deloc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For upload_data, this is the rule to start with:
upload_data 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 Deloc, apply this rule, and every upload_data call is checked against it from then on.
Questions about upload_data
Upload or replace a data file (CSV, JSON, TSV, XML, TXT, max 10MB) inside an already-deployed Deloc app WITHOUT redeploying. Use this to refresh dashboard data from databases or APIs on a schedule. The file is served at the same URL as the rest of the app, so client code that does fetch(. It is categorised as a Write tool in the Deloc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Deloc MCP server in PolicyLayer and add a rule for upload_data: 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 Deloc. Nothing to install.
upload_data 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_data 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_data. 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_data is provided by the Deloc MCP server (delocdev/deloc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Deloc, and thousands of servers like it.
This server
Across the catalogue