Run a multi-step image pipeline Chain multiple operations (resize, compress, convert, crop) in sequence. The image is fetched once, then each operation is applied to the output of the previous one. Max 10 operations per pipeline. Responses: 200: Processed image binary (Success Response) Content-T...
Part of the Image Processing server.
Free to start. No card required.
AI agents invoke image_pipeline to trigger processes or run actions in Image Processing. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
image_pipeline can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"image_pipeline": {
"limits": [
{
"counter": "image_pipeline_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Image Processing policy for all 7 tools.
These attack patterns abuse exactly the kind of access image_pipeline gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Run a multi-step image pipeline Chain multiple operations (resize, compress, convert, crop) in sequence. The image is fetched once, then each operation is applied to the output of the previous one. Max 10 operations per pipeline. 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 Execute tool in the Image Processing MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Image Processing MCP server in PolicyLayer and add a rule for image_pipeline: 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.
image_pipeline is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the image_pipeline 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 image_pipeline. 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.
image_pipeline 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.