retire_feature
Archive (retire) a feature so it stops showing to readers and agents, or restore a previously retired one. Safe-archive ONLY — never hard-deletes; retiring is fully reversible. Use when a feature is no longer accurate, was replaced, or the user says "remove this feature", "retire X", or "un-retir...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/retire-feature.md
What retire_feature does on Freedom Mcp
AI agents use retire_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 |
|---|---|---|---|
reason | string | — | Optional note on why this feature is being retired. |
restore | boolean | — | Set true to un-retire (restore) a previously archived feature. Default false. |
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.
Why retire_feature is rated Medium
Tool reversibly archives or restores features, never permanently deleting data.
From the tool's definition Safe-archive ONLY — never hard-deletes; retiring is fully reversible
Attacks that exploit this kind of access
The rule that runs retire_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 retire_feature, this is the rule to start with:
retire_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 retire_feature call is checked against it from then on.
Questions about retire_feature
Archive (retire) a feature so it stops showing to readers and agents, or restore a previously retired one. Safe-archive ONLY — never hard-deletes; retiring is fully reversible. Use when a feature is no longer accurate, was replaced, or the user says "remove this feature", "retire X", or "un-retire X". [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.
retire_feature accepts 4 parameters: reason, restore, companyId, feature_id. 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 retire_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.
retire_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 retire_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 retire_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.
retire_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