MCP Server Policy

CLOUDINARY MCP POLICY

Enforce policies on every tool call to the Cloudinary MCP Server. 7 tools listed, categorised, and ready for rules.

cloudinary/mcp-servers 1 read 6 write 7 tools total
cloudinary media image-management cdn

GET STARTED

Download this policy scaffold and add your rules. Intercept enforces them on every tool call before it reaches Cloudinary.

terminal

# Download policy scaffold

curl -o cloudinary.yaml https://raw.githubusercontent.com/policylayer/intercept/main/policies/cloudinary.yaml

# Run with Intercept

intercept --policy cloudinary.yaml -- npx -y @cloudinary/mcp-servers

Server documentation: https://github.com/cloudinary/mcp-servers

READ TOOLS

1

WRITE TOOLS

2

OTHER TOOLS

4

POLICY YAML

This scaffold lists every tool with empty rules. Add conditions — rate limits, argument validation, deny rules — then deploy with Intercept.

cloudinary.yaml
version: "1"
description: "Policy for cloudinary/mcp-servers"
default: "allow"
tools:
    get-tx-reference:
        rules: []
    upload:
        rules: []
    transform-asset:
        rules: []
    search:
        rules: []
    get-asset:
        rules: []
    update-asset:
        rules: []
    generate-archive:
        rules: []

FREQUENTLY ASKED QUESTIONS

What tools does the Cloudinary MCP server expose?

The Cloudinary MCP Server exposes 7 tools across 3 categories: Read, Write, Other. Each tool can be individually controlled with Intercept policies.

How do I enforce policies on Cloudinary?

Download the policy scaffold, add rules (rate limits, argument validation, deny rules), then run Intercept as a proxy in front of the Cloudinary MCP server. Every tool call is evaluated against your YAML policy before execution.

Is the Cloudinary policy free to use?

Yes. All Intercept policies are open source under the Apache 2.0 licence. Download, modify, and deploy without restrictions.

ENFORCE POLICIES ON CLOUDINARY

Open source. One binary. Zero dependencies.