request_content_revision
Request changes to a content item. Use when user says "revise this", "change the tone", "make it shorter", or provides feedback on pending content. The content will be re-transformed with their feedback. [write-tier — first use may require a manager's approval; a from-now-on approval makes future...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/request-content-revision.md
What request_content_revision does on Freedom Mcp
AI agents use request_content_revision 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 revise (get from get_pending_approvals) |
feedback | string | Yes | User's feedback on what to change (e.g., "make it shorter", "more professional tone") |
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 request_content_revision is rated Medium
This tool creates or modifies content items based on user feedback, which is a reversible Write operation. The approval gate ('first use may require a manager's approval') indicates organizational recognition of its write-tier sensitivity. Medium severity reflects that misuse would modify business content (marketing, communications, etc.) but is reversible and unlikely to cascade into financial or system-wide impact.
From the tool's definition Tool description states 'Request changes to a content item' and 'The content will be re-transformed with their feedback' — this modifies existing content reversibly.
Attacks that exploit this kind of access
The rule that runs request_content_revision 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 request_content_revision, this is the rule to start with:
request_content_revision 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 request_content_revision call is checked against it from then on.
Questions about request_content_revision
Request changes to a content item. Use when user says "revise this", "change the tone", "make it shorter", or provides feedback on pending content. The content will be re-transformed with their feedback. [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.
request_content_revision accepts 3 parameters: item_id, feedback, companyId. Required: item_id, feedback, 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 request_content_revision: 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.
request_content_revision 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 request_content_revision 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 request_content_revision. 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.
request_content_revision 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