complete_commitment
Mark a commitment as completed. Use when the user says they finished something or a deadline has passed. [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.]
This record as markdown: /tools/com-getfreedomos-freedom-mcp/complete-commitment.md
What complete_commitment does on Freedom Mcp
AI agents use complete_commitment 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 |
|---|---|---|---|
companyId | string | — | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
title_search | string | — | Search by title if ID not known (fuzzy match) |
commitment_id | string | — | The UUID of the commitment to complete |
Parameters from the server's own tool schema.
Why complete_commitment is rated Medium
This tool modifies commitment records by changing their status to completed. This is a reversible Write operation (the status can likely be reverted if needed). The '[write-tier — first use may require a manager's approval]' note indicates the system recognizes this as a data modification that warrants governance controls.
From the tool's definition Mark a commitment as completed
Attacks that exploit this kind of access
The rule that runs complete_commitment 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 complete_commitment, this is the rule to start with:
complete_commitment 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 complete_commitment call is checked against it from then on.
Questions about complete_commitment
Mark a commitment as completed. Use when the user says they finished something or a deadline has passed. [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.
complete_commitment accepts 3 parameters: companyId, title_search, commitment_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 complete_commitment: 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.
complete_commitment 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 complete_commitment 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 complete_commitment. 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.
complete_commitment 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