upload_image_from_url · Basis MCP Server MCP: Risk & Policy

WHAT IT DOES

What upload_image_from_url does on Basis MCP Server

AI agents use upload_image_from_url 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.

WHY IT NEEDS A POLICY

Why upload_image_from_url needs a policy

Uploading creates or adds data to IPFS/Pinata storage, making this a Write operation. It's not Read (no retrieval), Execute (no external command execution with variable effects), Destructive (reversible via deletion), or Financial (no monetary transaction). Severity is medium because while uploads are typically low-risk, they occur on a blockchain protocol with potential for spam, phishing content, or abuse.

From the tool's definition Tool description states "Upload an image from URL to Basis (Pinata/IPFS)", which is a create/write action that stores new data to a decentralized storage system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

upload_image_from_url Rate-limited

upload_image_from_url 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "upload_image_from_url": {
      "limits": [
        {
          "counter": "upload_image_from_url_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Basis MCP Server, so you can run agents against it safely.

FAQ

Questions about upload_image_from_url

What does the upload_image_from_url tool do? +

Upload an image from URL to Basis (Pinata/IPFS). Use purpose=. 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.

How do I enforce a policy on upload_image_from_url? +

Register the Basis MCP Server MCP server in PolicyLayer and add a rule for upload_image_from_url: 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.

What risk level is upload_image_from_url? +

upload_image_from_url is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit upload_image_from_url? +

Yes. Add a rate_limit block to the upload_image_from_url 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.

How do I block upload_image_from_url completely? +

Set action: deny in the PolicyLayer policy for upload_image_from_url. 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.

What MCP server provides upload_image_from_url? +

upload_image_from_url 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.