foundry_uploadFile
Upload a tenant file (POST /v1/foundry/files)
This record as markdown: /tools/onesi-genesis-mcp/foundry-uploadfile.md
What foundry_uploadFile does on Genesis
AI agents use foundry_uploadFile to create or update resources in Genesis, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Genesis environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
purpose | string | — | What the file is for, e.g. fine-tune or batch |
filename | string | Yes | File name stored with the upload |
mime_type | string | — | Optional media type, e.g. application/jsonl (default: from the filename extension; Foundry refuses application/octet-stream) |
content_base64 | string | Yes | Explicit standard-base64 content of the file (decoded 1 byte to 8 MiB) |
Parameters from the server's own tool schema.
Why foundry_uploadFile is rated Medium
An AI agent can call foundry_uploadFile faster than any human can review: one bad instruction and it creates or modifies resources in Genesis by the hundred, each call as confident as the last.
Risk signalsAccepts file system path (filename)
Attacks that exploit this kind of access
The rule that runs foundry_uploadFile safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Genesis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For foundry_uploadFile, this is the rule to start with:
foundry_uploadFile 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 Genesis, apply this rule, and every foundry_uploadFile call is checked against it from then on.
Questions about foundry_uploadFile
Upload a tenant file (POST /v1/foundry/files). It is categorised as a Write tool in the Genesis MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
foundry_uploadFile accepts 4 parameters: purpose, filename, mime_type, content_base64. Required: filename, content_base64. The full parameter table on this page comes from the server's own tool schema.
Register the Genesis MCP server in PolicyLayer and add a rule for foundry_uploadFile: 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 Genesis. Nothing to install.
foundry_uploadFile 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 foundry_uploadFile 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 foundry_uploadFile. 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.
foundry_uploadFile is provided by the Genesis MCP server (@onesi/genesis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Genesis, and thousands of servers like it.
This server
Across the catalogue