update_tactic
Update an existing tactic. Can identify by title instead of ID. Can modify title, description (the how-to / instructions), status, category, assigned_to, or re-bind it to an OKR key result (objective_id / linked_kr_id). [write-tier — first use may require a manager's approval; a from-now-on appro...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/update-tactic.md
What update_tactic does on Freedom Mcp
AI agents use update_tactic 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 |
status | string | — | New status |
category | string | — | New category |
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
tactic_id | string | — | ID of the tactic to update (optional if using tactic_title) |
assigned_to | string | — | User ID or "me"/"current_user" to assign to |
description | string | — | New description |
linked_kr_id | string | — | Key-result id the tactic most advances (validated against the company OKRs; takes precedence over objective_id, and its parent objective is derived). Unresolvab |
objective_id | string | — | OKR objective UUID to re-bind this tactic to (validated against this company); its most off-track key result is chosen. Unresolvable → binding cleared to null. |
tactic_title | string | — | Title of the tactic to update (use this or tactic_id) |
Parameters from the server's own tool schema.
Why update_tactic is rated Medium
This tool creates or modifies data (title, description, status, category, assignments, OKR bindings) in a reversible manner. These changes can be undone or corrected by subsequent updates. The [write-tier] notation and approval mechanism confirm Write classification.
From the tool's definition Update an existing tactic. Can modify title, description, status, category, assigned_to, or re-bind it to an OKR key result. Tool description explicitly indicates modification of reversible operational data.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs update_tactic 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_tactic, this is the rule to start with:
update_tactic 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_tactic call is checked against it from then on.
Questions about update_tactic
Update an existing tactic. Can identify by title instead of ID. Can modify title, description (the how-to / instructions), status, category, assigned_to, or re-bind it to an OKR key result (objective_id / linked_kr_id). [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_tactic accepts 10 parameters: title, status, category, companyId, tactic_id, assigned_to, description, linked_kr_id, objective_id, tactic_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_tactic: 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_tactic 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_tactic 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_tactic. 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_tactic 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