Upload a file to a FuseBase page. The file content must be provided as base64-encoded data. Returns the attachment ID and URL path. Use get_page_attachments to list existing attachments.
AI agents use upload_file to create or update resources in Fusebase MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fusebase MCP Server environment.
This tool creates and stores a new file attachment on a page, which is a reversible write operation. While it modifies the system state by adding data, it does not execute arbitrary code, destroy data, or move funds. The severity is medium rather than low because uncontrolled file uploads could consume storage, introduce malicious content, or expose sensitive information depending on downstream processing.
From the tool's definition Tool description states it "Upload[s] a file to a FuseBase page" and "Returns the attachment ID and URL path", indicating creation of new data artifacts.
Attacks that exploit this kind of access
Upload a file to a FuseBase page. The file content must be provided as base64-encoded data. Returns the attachment ID and URL path. Use get_page_attachments to list existing attachments. It is categorised as a Write tool in the Fusebase MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fusebase MCP Server MCP server in PolicyLayer and add a rule for 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 Fusebase MCP Server. Nothing to install.
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 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 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.
upload_file is provided by the Fusebase MCP Server MCP server (ryan-haver/fusebase-mcp). 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 →