promote_corpus_to_content
Mint the NEXT content angle(s) from the company's corpus into content_ideas + Command Center cards. Default count is 1 — do NOT bulk-fill the queue. For day-to-day drafting, prefer list_knowledge / read_knowledge (or list_corpus_inventory) to pull one chapter/passage JIT — that avoids re-tokenizi...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/promote-corpus-to-content.md
What promote_corpus_to_content does on Freedom Mcp
AI agents use promote_corpus_to_content 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 |
|---|---|---|---|
count | number | — | How many angles (1-3, default 1). Prefer 1. |
theme | string | — | Optional focus (e.g. "Harness principles", "pharmacy USP") |
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 promote_corpus_to_content is rated Medium
This tool creates new data records (content_ideas and Command Center cards) from existing corpus material. It is reversible (content can be edited or removed), so it falls under Write rather than Destructive. The approval requirement and medium severity reflect that bulk misuse could pollute the content queue, but individual writes are recoverable.
From the tool's definition Tool description states it will 'Mint the NEXT content angle(s)...into content_ideas + Command Center cards' and 'creates' new content artifacts from corpus material. The description explicitly mentions this is 'write-tier' requiring approval.
Attacks that exploit this kind of access
The rule that runs promote_corpus_to_content 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 promote_corpus_to_content, this is the rule to start with:
promote_corpus_to_content 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 promote_corpus_to_content call is checked against it from then on.
Questions about promote_corpus_to_content
Mint the NEXT content angle(s) from the company's corpus into content_ideas + Command Center cards. Default count is 1 — do NOT bulk-fill the queue. For day-to-day drafting, prefer list_knowledge / read_knowledge (or list_corpus_inventory) to pull one chapter/passage JIT — that avoids re-tokenizing the whole book. Use promote only when a human-facing card is needed (weekly queue, Held post, operator asked). Faith grain: angles only. Never invent from empty corpus. [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.
promote_corpus_to_content accepts 3 parameters: count, theme, 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 promote_corpus_to_content: 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.
promote_corpus_to_content 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 promote_corpus_to_content 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 promote_corpus_to_content. 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.
promote_corpus_to_content 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