update_pipeline
Update an existing content pipeline. Use when user says "rename my pipeline", "change the pipeline name", "update pipeline settings", or wants to modify pipeline configuration. Can update name, persona, ICPs, output type, or destination. [write-tier — first use may require a manager's approval; a...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/update-pipeline.md
What update_pipeline does on Freedom Mcp
AI agents use update_pipeline to create or update resources in Freedom Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Freedom Mcp environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | New name for the pipeline |
output | string | — | New output type |
icp_ids | array | — | New list of ICP IDs to target |
persona | string | — | New persona ID to use for transformations |
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
destination | string | — | Where to publish: freedom_os (auto-publish to platform), manual (copy/paste). Social platforms (x/linkedin/instagram/facebook/threads) publish via the gated own |
pipeline_id | string | Yes | ID of the pipeline to update (get from list_pipelines) |
Parameters from the server's own tool schema.
Why update_pipeline is rated Medium
This tool creates or modifies data reversibly. It updates pipeline configuration (name, persona, ICPs, output type, destination) but does not delete or irreversibly destroy data. The write-tier approval requirement and reversible nature of configuration updates place it in the Write category.
From the tool's definition Tool description explicitly states 'Update an existing content pipeline' and 'Can update name, persona, ICPs, output type, or destination.' The write-tier governance note confirms this modifies configuration without deletion or irreversible consequences.
Risk signalsAccepts file system path (destination)
Attacks that exploit this kind of access
The rule that runs update_pipeline safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freedom Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_pipeline, this is the rule to start with:
update_pipeline 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Freedom Mcp, apply this rule, and every update_pipeline call is checked against it from then on.
Questions about update_pipeline
Update an existing content pipeline. Use when user says "rename my pipeline", "change the pipeline name", "update pipeline settings", or wants to modify pipeline configuration. Can update name, persona, ICPs, output type, or destination. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.]. It is categorised as a Write tool in the Freedom Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_pipeline accepts 7 parameters: name, output, icp_ids, persona, companyId, destination, pipeline_id. Required: companyId, pipeline_id. The full parameter table on this page comes from the server's own tool schema.
Register the Freedom MCP server in PolicyLayer and add a rule for update_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 Freedom Mcp. Nothing to install.
update_pipeline 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 update_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 update_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.
update_pipeline is provided by the Freedom MCP server (https://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freedom, and thousands of servers like it.
This server
Across the catalogue