Upload a local image file to Basis (Pinata/IPFS). For agents/Claude Code with local file access.
AI agents use upload_image_from_file to create or update resources in Basis MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Basis MCP Server environment.
Uploading an image to IPFS/Pinata is a reversible write operation—it creates a new resource without modifying or deleting existing data. The blast radius is low because image uploads have minimal systemic impact on the blockchain or financial operations.
From the tool's definition Tool description states 'Upload a local image file to Basis (Pinata/IPFS)', indicating a create/store operation that adds data to a distributed storage system.
Attacks that exploit this kind of access
Upload a local image file to Basis (Pinata/IPFS). For agents/Claude Code with local file access. It is categorised as a Write tool in the Basis MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Basis MCP Server MCP server in PolicyLayer and add a rule for upload_image_from_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 Basis MCP Server. Nothing to install.
upload_image_from_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_image_from_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_image_from_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_image_from_file is provided by the Basis MCP Server MCP server (launch-on-basis/mcp-ts). 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 →