High Risk →

image_scale_by_size

image_scale_by_size

How to control image_scale_by_size ↓

AI agents invoke image_scale_by_size to trigger actions in Qiniu MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

High Risk

Image scaling is a computational operation that transforms data and produces output, classifying it as Execute rather than Read. The severity is medium because unintended image scaling could degrade service quality or consume computational resources, but lacks the irreversibility of Destructive operations or financial impact.

From the tool's definition Tool name is 'image_scale_by_size' with empty description. Based on sibling tools (image_round_corner, image_scale_by_percent) which perform image transformation operations, this tool likely executes image processing operations on stored objects.

Documented attack patterns abuse exactly the kind of access image_scale_by_size gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Qiniu MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for image_scale_by_size:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "image_scale_by_size": {
      "limits": [
        {
          "counter": "image_scale_by_size_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

image_scale_by_size stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Qiniu MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the image_scale_by_size tool do? +

image_scale_by_size. It is categorised as a Execute tool in the Qiniu MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on image_scale_by_size? +

Register the Qiniu MCP Server MCP server in PolicyLayer and add a rule for image_scale_by_size: 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 Qiniu MCP Server. Nothing to install.

What risk level is image_scale_by_size? +

image_scale_by_size is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit image_scale_by_size? +

Yes. Add a rate_limit block to the image_scale_by_size 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 image_scale_by_size completely? +

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

image_scale_by_size is provided by the Qiniu MCP Server MCP server (qiniu/qiniu-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Qiniu MCP Server tool call.

Deterministic rules across all 24 Qiniu MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

24 Qiniu MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.