ratify_capability

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

Medium RISK CLASS

Category Write

Parameters 32 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/ratify-capability.md

WHAT IT DOES

What ratify_capability does on Freedom Mcp

AI agents use ratify_capability 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
`features`	array	Yes	The operator-confirmed features to persist. Each needs a title; description/solves/evidence/feature_id optional.
`companyId`	string	Yes	FreedomOS company id to act within (you must be a member). Required for company-scoped tools.
`scan_hash`	string	—	Optional repo commit SHA the derivation came from (recorded for re-scan reconciliation).

Parameters from the server's own tool schema.

RISK

Why ratify_capability is rated Medium

This tool creates or modifies data (product capability metadata) in a central, authoritative index. While the modification is reversible (idempotent updates), the impact is significant because these features inform downstream business agents and governance (Integrity Gate). The sensitive-tier designation with manager approval requirement signals organizational risk awareness.

From the tool's definition Persists operator-confirmed derived features into the product capability index as source='derived'. Tool explicitly updates an authoritative data structure ('becomes an authoritative capability') via idempotent writes ('re-ratifying updates in place').

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

ratify_capability Rate-limited

ratify_capability 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": {
    "ratify_capability": {
      "limits": [
        {
          "counter": "ratify_capability_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 ratify_capability call is checked against it from then on.

FAQ

Questions about ratify_capability

What does the ratify_capability tool do? +

Persist the operator-CONFIRMED derived features (from derive_capability) into the product capability index as source='derived'. Call ONLY with features the operator has ratified — each then becomes an authoritative capability the marketing agents and the Integrity Gate use. Idempotent (re-ratifying updates in place). Derived can't-do limits are drafted for awareness but authored separately for now. Routing: Operator confirmed the derived features from derive_capability → persist them with this [sensitive-tier — EVERY call needs a manager's approval (per-send human rail): each request queues its own approval card and sends exactly once on approve. There is no standing grant for this tool.]. 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 ratify_capability accept? +

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

How do I enforce a policy on ratify_capability? +

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

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

Can I rate-limit ratify_capability? +

Yes. Add a rate_limit block to the ratify_capability 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 ratify_capability completely? +

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

ratify_capability 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

The MCP Attack Database →

Guides

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