Medium Risk

resize_image

调整图片大小

How to control resize_image ↓

AI agents use resize_image to create or update resources in Docx_MCP_cj — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Docx_MCP_cj environment.

Medium Risk

Resizing an image modifies document content reversibly without deleting data. This is a Write operation—it changes state but can be undone (resized again or reverted). The blast radius is medium because bulk or incorrect resizing could degrade document visual integrity or cause formatting issues, but the operation itself is not destructive or irreversible.

From the tool's definition Tool name is 'resize_image'; description translates to 'adjust image size'. This modifies image properties within a document.

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

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

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

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

  1. Create a free account and register Docx_MCP_cj — 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.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the resize_image tool do? +

调整图片大小. It is categorised as a Write tool in the Docx_MCP_cj MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on resize_image? +

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

What risk level is resize_image? +

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

Can I rate-limit resize_image? +

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

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

resize_image is provided by the Docx_MCP_cj MCP server (rockcj/docx_mcp_cj). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Docx_MCP_cj tool call.

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

Free to start. No card required.

54 Docx_MCP_cj 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.