update_feature_status

SERVERFreedom Mcp SOURCEhttps://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp

Medium RISK CLASS

Category Write

Parameters 33 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-getfreedomos-freedom-mcp/update-feature-status.md

WHAT IT DOES

What update_feature_status does on Freedom Mcp

AI agents use update_feature_status 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
`status`	string	Yes	New status for the feature
`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

Parameters from the server's own tool schema.

RISK

Why update_feature_status is rated Medium

This tool modifies feature metadata/status in a business-ops system. It is a Write operation because it creates or updates data state reversibly—the status can be changed again later. Severity is medium because misuse could promote unfinished or problematic features to marketing, causing reputational harm or customer-facing issues, but the action is not irreversible and does not move money.

From the tool's definition Tool name 'update_feature_status' and description 'Mark a feature as ready for marketing' indicates data modification. The approval tier annotation confirms it creates a reversible state change (marking status), not irreversible deletion or code execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_feature_status 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_status, this is the rule to start with:

update_feature_status Rate-limited

update_feature_status 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_feature_status": {
      "limits": [
        {
          "counter": "update_feature_status_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Freedom Mcp, apply this rule, and every update_feature_status call is checked against it from then on.

FAQ

Questions about update_feature_status

What does the update_feature_status tool do? +

Mark a feature as ready for marketing. Use when user says "mark X as ready", "this feature is ready to market", or wants to highlight a feature for marketing content. [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.

What parameters does update_feature_status accept? +

update_feature_status accepts 3 parameters: status, companyId, feature_id. Required: status, companyId, feature_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_feature_status? +

Register the Freedom MCP server in PolicyLayer and add a rule for update_feature_status: 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.

What risk level is update_feature_status? +

update_feature_status is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_feature_status? +

Yes. Add a rate_limit block to the update_feature_status 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.

How do I block update_feature_status completely? +

Set action: deny in the PolicyLayer policy for update_feature_status. 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.

What MCP server provides update_feature_status? +

update_feature_status 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.

KEEP EXPLORING

More on Freedom, and thousands of servers like it.

This server

All 238 Freedom tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →