list_pipelines
List all content pipelines (changelogs, team updates, reports, customer newsletters, social posts). Use when user asks about their content automation, "what content am I publishing?", "show my pipelines", or "what outputs are configured". Output types: changelog (public product updates), team_upd...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/list-pipelines.md
What list_pipelines does on Freedom Mcp
AI agents call list_pipelines to retrieve information from Freedom Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
Parameters from the server's own tool schema.
Why list_pipelines is rated Low
This tool retrieves and displays information about existing content pipelines without creating, modifying, deleting, or executing any operations. It is a pure read operation that queries configuration data. The low severity reflects minimal risk if misused by an AI agent—exposure would be limited to information disclosure about the organization's content publishing setup.
From the tool's definition Tool description states 'List all content pipelines' and 'Use when user asks about their content automation, "what content am I publishing?", "show my pipelines"'.
Attacks that exploit this kind of access
The rule that runs list_pipelines 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 list_pipelines, this is the rule to start with:
list_pipelines is read-only, so it stays allowed. 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 list_pipelines call is checked against it from then on.
Questions about list_pipelines
List all content pipelines (changelogs, team updates, reports, customer newsletters, social posts). Use when user asks about their content automation, "what content am I publishing?", "show my pipelines", or "what outputs are configured". Output types: changelog (public product updates), team_update (internal team email via Freedom OS), report (email to specific recipients), customer_newsletter (external customers - requires user Email MCP like Mailchimp), social_post (x/linkedin/instagram/facebook/threads via the gated publish owner). It is categorised as a Read tool in the Freedom Mcp MCP Server, which means it retrieves data without modifying state.
list_pipelines accepts 1 parameter: companyId. Required: companyId. 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 list_pipelines: 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.
list_pipelines is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_pipelines 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 list_pipelines. 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.
list_pipelines 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