This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/cloudinary-get-usage.md
What cloudinary_get_usage does on UnClick
AI agents call cloudinary_get_usage to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
api_key | string | Yes | Cloudinary API key |
api_secret | string | Yes | Cloudinary API secret |
cloud_name | string | Yes | Cloudinary cloud name |
Parameters from the server's own tool schema.
Why cloudinary_get_usage is rated Low
This tool retrieves usage metrics and quota information from Cloudinary, which is a read-only operation with no side effects. It does not create, modify, delete, or execute code. The blast radius of misuse is minimal—an attacker could only view usage data, not affect services or incur charges. Severity is low because this is informational access only.
From the tool's definition Tool name 'cloudinary_get_usage' and description 'Get Cloudinary usage and quota' indicate a retrieval operation that queries account usage statistics without modifying or deleting data.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs cloudinary_get_usage safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cloudinary_get_usage, this is the rule to start with:
cloudinary_get_usage is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every cloudinary_get_usage call is checked against it from then on.
Questions about cloudinary_get_usage
Get Cloudinary usage and quota. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
cloudinary_get_usage accepts 3 parameters: api_key, api_secret, cloud_name. Required: api_key, api_secret, cloud_name. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for cloudinary_get_usage: 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 UnClick. Nothing to install.
cloudinary_get_usage is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the cloudinary_get_usage 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 cloudinary_get_usage. 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.
cloudinary_get_usage is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue