run_design_pipeline · AI-Canvas MCP Server MCP

WHAT IT DOES

What run_design_pipeline does on AI-Canvas MCP Server

AI agents invoke run_design_pipeline to trigger actions in AI-Canvas 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.

WHY IT NEEDS A POLICY

Why run_design_pipeline needs a policy

This tool runs a multi-stage pipeline that orchestrates other design operations (seen in sibling tools: apply_brand_profile, apply_operations, create_mockup). Pipelines are Execute category because they trigger sequences of dependent actions.

From the tool's definition Tool name and description explicitly state 'Execute a full design workflow' — this triggers automated operations across multiple design stages (brand application, mockup generation, export).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_design_pipeline Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_design_pipeline": {
      "limits": [
        {
          "counter": "run_design_pipeline_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches AI-Canvas MCP Server, so you can run agents against it safely.

FAQ

Questions about run_design_pipeline

What does the run_design_pipeline tool do? +

Execute a full design workflow from brand to mockup. It is categorised as a Execute tool in the AI-Canvas 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 run_design_pipeline? +

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

What risk level is run_design_pipeline? +

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

Can I rate-limit run_design_pipeline? +

Yes. Add a rate_limit block to the run_design_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.

How do I block run_design_pipeline completely? +

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

What MCP server provides run_design_pipeline? +

run_design_pipeline is provided by the AI-Canvas MCP Server MCP server (laoluojuhai/ai-canvas). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.