AI agents use upload to create or update resources in Moxis — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Moxis environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | moxis instance url or alias |
path | string | Yes | path to pdf file |
Parameters from the server's own tool schema.
The upload function creates or adds a new document to MOXIS and generates a corresponding URL. This is a reversible write operation—documents can typically be deleted or modified later. It does not execute arbitrary code, delete data irreversibly, or move money.
From the tool's definition Tool description states it 'uploads document to MOXIS and returns an url', which is a create/write operation that adds new data to the system.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
uploads document to MOXIS and returns an url. It is categorised as a Write tool in the Moxis MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
upload accepts 2 parameters: id, path. Required: id, path. The full parameter table on this page comes from the server's own tool schema.
Register the Moxis MCP server in PolicyLayer and add a rule for upload: 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 Moxis. Nothing to install.
upload 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 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. 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 is provided by the Moxis MCP server (@xitrust-pub/moxis-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →