New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

pipeline_set_placement

Save where a campaign / webhook / deal-pipeline node sits on the journey canvas (upsert by kind + ref_id). Layout only. Returns {data: Placement}.

SERVERMax MCP Server SOURCEdigital-crew-technologies/max-mcp-server
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/digital-crew-technologies-max-mcp-server/pipeline-set-placement.md

What pipeline_set_placement does on Max MCP Server

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

Why pipeline_set_placement is rated Medium

Updates position metadata on a journey canvas; reversible and non-destructive configuration change.

From the tool's definition Save...placement...upsert by kind + ref_id. Layout only.

Questions about pipeline_set_placement

What does the pipeline_set_placement tool do? +

Save where a campaign / webhook / deal-pipeline node sits on the journey canvas (upsert by kind + ref_id). Layout only. Returns {data: Placement}. It is categorised as a Write tool in the Max MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on pipeline_set_placement? +

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

What risk level is pipeline_set_placement? +

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

Can I rate-limit pipeline_set_placement? +

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

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

pipeline_set_placement is provided by the Max MCP Server MCP server (digital-crew-technologies/max-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Max MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Max MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.