update_key_result
Update a key result for the company operator and any agent owning KR progress (progress, assignment, due date, rename, measure binding). Use when work moves a Key Result and you need to log current value, reassign, rename, or bind a measure source. Prefer key_result_id — the parent objective is r...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/update-key-result.md
What update_key_result does on Freedom Mcp
AI agents use update_key_result 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 display title for the key result (rename) |
due_date | string | — | Due date (YYYY-MM-DD format) |
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
start_date | string | — | Start date (YYYY-MM-DD format) |
assigned_to | string | — | User ID to assign this KR to. Use "me" or "current_user" to assign to the current user. |
objective_id | string | — | ID of the parent objective (optional when key_result_id is set — id resolves the parent) |
target_value | number | — | Target value to achieve |
current_value | number | — | Current progress value |
key_result_id | string | — | Stable KR id (preferred). Parent objective is looked up from the KR row across active objectives — do not re-search by fuzzy objective title. |
measure_source | string | — | Bind current progress to a live data source (auto-updated daily by the OKR health sweep). One of: stripe_active_subscribers, stripe_mrr, crm_active_leads. Pass |
objective_title | string | — | Title of the parent objective (optional when key_result_id is set — id resolves the parent) |
key_result_title | string | — | Title of the key result to update (use this OR key_result_id) — matched against the CURRENT title, even when also renaming |
Parameters from the server's own tool schema.
Why update_key_result is rated Medium
This tool creates or modifies business data (key results, assignments, due dates) without deleting or permanently destroying records. Updates are reversible through subsequent calls. The blast radius is medium because misconfiguration could misalign company OKRs and agent assignments, but changes are auditable and correctable.
From the tool's definition Tool description states: 'Update a key result' and 'Use when work moves a Key Result and you need to log current value, reassign, rename, or bind a measure source.' The tool modifies KR progress, assignment, due date, and rename fields—all reversible updates.
Risk signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
The rule that runs update_key_result 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_key_result, this is the rule to start with:
update_key_result 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_key_result call is checked against it from then on.
Questions about update_key_result
Update a key result for the company operator and any agent owning KR progress (progress, assignment, due date, rename, measure binding). Use when work moves a Key Result and you need to log current value, reassign, rename, or bind a measure source. Prefer key_result_id — the parent objective is resolved from the KR row (no fuzzy title search). Title match is a fallback; resolution uses the EXISTING title even when renaming in the same call. A missing/archived KR returns one terminal recovery with live alternatives — do not retry the same args. [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_key_result accepts 12 parameters: title, due_date, companyId, start_date, assigned_to, objective_id, target_value, current_value, key_result_id, measure_source, objective_title, key_result_title. Required: companyId. 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_key_result: 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_key_result 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_key_result 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_key_result. 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_key_result 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