approve_pipeline_item
Approve a content item for publishing — or REJECT it with approved:false. Use when user says "approve it", "looks good", "publish that" (approve), or "reject it", "drop that duplicate", "don't publish" (approved:false). [sensitive-tier — first use may require a manager's approval; a from-now-on a...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/approve-pipeline-item.md
What approve_pipeline_item does on Freedom Mcp
AI agents use approve_pipeline_item 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 |
|---|---|---|---|
item_id | string | Yes | ID of the pipeline output to approve (get from get_pending_approvals) |
approved | boolean | — | Default true. Pass false to REJECT: the item is marked rejected and leaves the approval queue — it never publishes. An explicit false can never approve. |
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 approve_pipeline_item is rated Medium
This tool modifies the state of content items (approval status) reversibly—it changes a publishing decision but does not permanently delete data. The action is Write rather than Execute because it updates a specific business object's metadata rather than triggering arbitrary external code. It is not Destructive because rejection/non-approval is reversible (the content can be re-submitted).
From the tool's definition Approve a content item for publishing — or REJECT it with approved:false. Use when user says "approve it", "looks good", "publish that" (approve), or "reject it", "drop that duplicate", "don't publish" (approved:false).
Attacks that exploit this kind of access
The rule that runs approve_pipeline_item 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 approve_pipeline_item, this is the rule to start with:
approve_pipeline_item 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 approve_pipeline_item call is checked against it from then on.
Questions about approve_pipeline_item
Approve a content item for publishing — or REJECT it with approved:false. Use when user says "approve it", "looks good", "publish that" (approve), or "reject it", "drop that duplicate", "don't publish" (approved:false). [sensitive-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.
approve_pipeline_item accepts 3 parameters: item_id, approved, companyId. Required: item_id, 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 approve_pipeline_item: 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.
approve_pipeline_item 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 approve_pipeline_item 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 approve_pipeline_item. 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.
approve_pipeline_item 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