update_feature
Update fields on an existing Feature Index entry — title, description, category, solves, limits, or demo_url. Use when the user wants to correct or enrich a feature's marketing copy. To change status use update_feature_status; to remove a feature from view use retire_feature — never delete. [writ...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/update-feature.md
What update_feature does on Freedom Mcp
AI agents use update_feature 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 |
|---|---|---|---|
title | string | — | Display title (e.g., "AI Content Pipeline") |
limits | string | — | Current limitations |
solves | array | — | Problems/pain points this feature solves |
category | string | — | Category (e.g., "ai", "marketing", "finance", "automation") |
demo_url | string | — | URL to a demo video (Screen Studio, Loom, etc.) |
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
feature_id | string | Yes | The feature_id slug (e.g., "ai-content-pipeline") or UUID. |
description | string | — | Marketing-ready description of the feature |
Parameters from the server's own tool schema.
Why update_feature is rated Medium
This tool modifies data (Feature Index entries) reversibly without deletion or financial impact. It updates marketing metadata (title, description, category, URLs) that can be changed again or rolled back. The tool explicitly delegates destructive operations to separate tools (update_feature_status, retire_feature) and forbids deletion ('never delete'), confirming it is purely Write, not Destructive.
From the tool's definition Tool description states 'Update fields on an existing Feature Index entry — title, description, category, solves, limits, or demo_url' and explicitly creates reversible changes via update operations.
Attacks that exploit this kind of access
The rule that runs update_feature 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 update_feature, this is the rule to start with:
update_feature 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 update_feature call is checked against it from then on.
Questions about update_feature
Update fields on an existing Feature Index entry — title, description, category, solves, limits, or demo_url. Use when the user wants to correct or enrich a feature's marketing copy. To change status use update_feature_status; to remove a feature from view use retire_feature — never delete. [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.
update_feature accepts 8 parameters: title, limits, solves, category, demo_url, companyId, feature_id, description. Required: companyId, feature_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 update_feature: 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.
update_feature 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 update_feature 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 update_feature. 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.
update_feature 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