update_commitment
Update fields of an existing commitment — title, domain, due date, consequence, or description. Use when the user says "change the due date on...", "rename that commitment to...", "move X to next week", or otherwise edits something already tracked (not marking it done — use complete_commitment fo...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/update-commitment.md
What update_commitment does on Freedom Mcp
AI agents use update_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 |
|---|---|---|---|
title | string | — | New title. |
domain | string | — | New life domain: personal, family, home, w2, or company:<name>. |
due_date | string | — | New due date in YYYY-MM-DD format. |
companyId | string | — | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
consequence | string | — | New consequence — what happens if this slips. |
description | string | — | New additional details or notes. |
title_search | string | — | Search by title if ID not known (fuzzy match). |
commitment_id | string | — | The UUID of the commitment to update. |
Parameters from the server's own tool schema.
Why update_commitment is rated Medium
This is a Write operation: it creates or modifies data reversibly without deleting or executing external code. The modifications (renaming, rescheduling, editing descriptions) can be undone by subsequent update calls.
From the tool's definition Tool description explicitly states it updates existing commitment fields: 'title, domain, due date, consequence, or description' and contrasts with 'complete_commitment' for marking done.
Attacks that exploit this kind of access
The rule that runs update_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 update_commitment, this is the rule to start with:
update_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 update_commitment call is checked against it from then on.
Questions about update_commitment
Update fields of an existing commitment — title, domain, due date, consequence, or description. Use when the user says "change the due date on...", "rename that commitment to...", "move X to next week", or otherwise edits something already tracked (not marking it done — use complete_commitment for that). [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_commitment accepts 8 parameters: title, domain, due_date, companyId, consequence, description, 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 update_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.
update_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 update_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 update_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.
update_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