Upload a file to a workspace (max 10MB). Pass content as base64. Use to provide input data, fixtures, or templates that a VM will consume — file lands in the workspace and can be referenced by computers in it.
AI agents use orgo_upload_file to create or update resources in Orgo MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Orgo MCP Server environment.
This tool creates or modifies files in a managed workspace environment. The action is reversible (files can be deleted), and while it could be misused to inject malicious payloads or credentials, the blast radius is constrained by the 10MB limit and workspace isolation.
From the tool's definition Tool description explicitly states 'Upload a file to a workspace' and 'file lands in the workspace and can be referenced by computers in it', indicating file creation/modification with reversible effects.
Documented attack patterns abuse exactly the kind of access orgo_upload_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Orgo MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for orgo_upload_file:
{
"version": "1",
"default": "deny",
"tools": {
"orgo_upload_file": {
"limits": [
{
"counter": "orgo_upload_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}orgo_upload_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.
Free to start. No card required.
Upload a file to a workspace (max 10MB). Pass content as base64. Use to provide input data, fixtures, or templates that a VM will consume — file lands in the workspace and can be referenced by computers in it. It is categorised as a Write tool in the Orgo MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Orgo MCP Server MCP server in PolicyLayer and add a rule for orgo_upload_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 Orgo MCP Server. Nothing to install.
orgo_upload_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 orgo_upload_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 orgo_upload_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.
orgo_upload_file is provided by the Orgo MCP Server MCP server (nickvasilescu/orgo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Orgo MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
28 Orgo MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.