resolve_work
Mark a shared work-graph item resolved — verified (default), published, or cancelled. In the full system, resolving an item cascades to unblock items that depend on it, so this is a process-initiator. Optionally record a verified_outcome. [sensitive-tier, initiates a multi-step agent process — fi...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/resolve-work.md
What resolve_work does on Freedom Mcp
AI agents invoke resolve_work to trigger actions in Freedom Mcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
status | string | — | Terminal status (default "verified"). |
outcome | object | — | Optional structured verified_outcome to record. |
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
work_item_id | string | Yes | UUID of the lab_work_items row to resolve. |
Parameters from the server's own tool schema.
Why resolve_work is rated High
Resolving triggers cascading multi-step agent processes, making it an Execute-tier operation with broad side effects.
From the tool's definition cascades to unblock items that depend on it, process-initiator
Attacks that exploit this kind of access
The rule that runs resolve_work 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 resolve_work, this is the rule to start with:
resolve_work stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 resolve_work call is checked against it from then on.
Questions about resolve_work
Mark a shared work-graph item resolved — verified (default), published, or cancelled. In the full system, resolving an item cascades to unblock items that depend on it, so this is a process-initiator. Optionally record a verified_outcome. [sensitive-tier, initiates a multi-step agent process — 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 Execute tool in the Freedom Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
resolve_work accepts 4 parameters: status, outcome, companyId, work_item_id. Required: companyId, work_item_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 resolve_work: 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.
resolve_work is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the resolve_work 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 resolve_work. 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.
resolve_work 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.
Across the catalogue