archive_pipeline

SERVERFreedom Mcp SOURCEhttps://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp

Medium RISK CLASS

Category Write

Parameters 42 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-getfreedomos-freedom-mcp/archive-pipeline.md

WHAT IT DOES

What archive_pipeline does on Freedom Mcp

AI agents use archive_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
`reason`	string	—	Optional. Why this pipeline is being archived or restored.
`restore`	boolean	—	Set true to REACTIVATE an archived pipeline instead of archiving it. Default false (archive).
`companyId`	string	Yes	FreedomOS company id to act within (you must be a member). Required for company-scoped tools.
`pipeline_id`	string	Yes	ID of the pipeline to archive/restore (get from list_pipelines)

Parameters from the server's own tool schema.

RISK

Why archive_pipeline is rated Medium

This tool modifies pipeline state (is_active flag) in a reversible manner without cascading deletes or permanent destruction. It does not execute external operations, move money, or irreversibly delete data. The requirement for manager approval on first use reflects write-level access control, consistent with data modification rather than reading or destructive operations.

From the tool's definition Tool description states it "flips is_active off/on" and "soft-delete/restore", indicating reversible state modification of a pipeline object.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs archive_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 archive_pipeline, this is the rule to start with:

archive_pipeline Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "archive_pipeline": {
      "limits": [
        {
          "counter": "archive_pipeline_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Freedom Mcp, apply this rule, and every archive_pipeline call is checked against it from then on.

FAQ

Questions about archive_pipeline

What does the archive_pipeline tool do? +

Archive (or restore) a content pipeline — flips is_active off/on, mirroring the Content Pipeline UI's soft-delete/restore. No data is deleted or cascaded. Use when the user says "archive this pipeline", "pause my newsletter automation", "turn off this pipeline", or "bring back my archived pipeline" (pass restore:true). [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.

What parameters does archive_pipeline accept? +

archive_pipeline accepts 4 parameters: reason, restore, companyId, pipeline_id. Required: companyId, pipeline_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on archive_pipeline? +

Register the Freedom MCP server in PolicyLayer and add a rule for archive_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.

What risk level is archive_pipeline? +

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

Can I rate-limit archive_pipeline? +

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

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

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

KEEP EXPLORING

More on Freedom, and thousands of servers like it.

This server

All 238 Freedom tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →