Resize an image Scale an image by a factor. Use 'scale' for uniform scaling, or 'scale_x'/'scale_y' for independent axes. Values are float factors (e.g. 0.5 = half size). Responses: 200: Processed image binary (Success Response) Content-Type: application/json Content-Type: image/jpeg Example Resp...
Part of the Image Processing server.
Free to start. No card required.
AI agents use resize_image to create or modify resources in Image Processing. 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 resize_image 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 Image Processing.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"resize_image": {
"limits": [
{
"counter": "resize_image_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Image Processing policy for all 7 tools.
These attack patterns abuse exactly the kind of access resize_image gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Resize an image Scale an image by a factor. Use 'scale' for uniform scaling, or 'scale_x'/'scale_y' for independent axes. Values are float factors (e.g. 0.5 = half size). Responses: 200: Processed image binary (Success Response) Content-Type: application/json Content-Type: image/jpeg Example Response: json "string" Content-Type: image/png Example Response: json "string" Content-Type: image/webp Example Response: json "string". It is categorised as a Write tool in the Image Processing MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Image Processing 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 Image Processing. Nothing to install.
resize_image is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
resize_image is provided by the Image Processing MCP server (https://api.pictomancer.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 Image Processing 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.