submit_content_to_pipeline
Submit manual content to a pipeline for transformation. Use when user says "add this to my changelog", "create a newsletter from this", "transform this content", or provides content to be processed. Content will be transformed using the pipeline's persona and ICPs. Social pipelines publish to the...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/submit-content-to-pipeline.md
What submit_content_to_pipeline does on Freedom Mcp
AI agents use submit_content_to_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 |
|---|---|---|---|
content | string | Yes | Raw content to transform (updates, notes, announcements, etc.) |
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 submit to (get from list_pipelines) |
media_artifact_ids | array | — | Optional. Artifact IDs (image or video, from generate_image_xai / generate_video, same company) to attach as media on this post. Required for visual social post |
Parameters from the server's own tool schema.
Why submit_content_to_pipeline is rated Medium
This tool creates or modifies content reversibly across multiple platforms (social media, newsletters, changelogs). While publication to social channels has broad reach, the action is: (1) reversible (content can be deleted/unpublished), (2) not financial, (3) not destructive, and (4) requires human approval before execution on social platforms, limiting autonomous misuse severity.
From the tool's definition Tool name 'submit_content_to_pipeline' and description state it 'Submit[s] manual content to a pipeline for transformation' and 'publish[es] to the pipeline's declared destination'; these are write operations that create or modify content in downstream…
Risk signalsAccepts raw HTML/template content (content)
Attacks that exploit this kind of access
The rule that runs submit_content_to_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 submit_content_to_pipeline, this is the rule to start with:
submit_content_to_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 submit_content_to_pipeline call is checked against it from then on.
Questions about submit_content_to_pipeline
Submit manual content to a pipeline for transformation. Use when user says "add this to my changelog", "create a newsletter from this", "transform this content", or provides content to be processed. Content will be transformed using the pipeline's persona and ICPs. Social pipelines publish to the pipeline's declared destination (x/linkedin/instagram/facebook/threads — set via update_pipeline; undeclared defaults to x) after human approval; instagram items REQUIRE media_artifact_ids. [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.
submit_content_to_pipeline accepts 4 parameters: content, companyId, pipeline_id, media_artifact_ids. Required: content, 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 submit_content_to_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.
submit_content_to_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 submit_content_to_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 submit_content_to_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.
submit_content_to_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