Medium Risk

upload

Upload media assets to Cloudinary CDN

Risk signalsUploads files to cloud storage

Part of the Cloudinary server.

upload can modify Cloudinary data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE CLOUDINARY →

Free to start. No card required.

AI agents use upload to create or modify resources in Cloudinary. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call upload repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Cloudinary.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "upload": {
      "limits": [
        {
          "counter": "upload_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Cloudinary policy for all 7 tools.

Get this rule live on your own Cloudinary server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY CLOUDINARY →

These attack patterns abuse exactly the kind of access upload gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so upload only ever does what you allow.

SECURE CLOUDINARY →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the upload tool do? +

Upload media assets to Cloudinary CDN. It is categorised as a Write tool in the Cloudinary 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? +

Register the Cloudinary 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 Cloudinary. Nothing to install.

What risk level is upload? +

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

Can I rate-limit upload? +

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.

How do I block upload completely? +

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.

What MCP server provides upload? +

upload is provided by the Cloudinary MCP server (@cloudinary/mcp-servers). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Cloudinary tool call.

Deterministic rules across all 7 Cloudinary tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.