generate_tactics
Generate AND save 5 grounded growth tactics for a 4-F category, composed from the company mission/vision, OKRs, and ICP customer profile. Persists them as growth_tactics (optionally bound to an objective, key result, and lane). Use when an agent should author concrete tactics for a goal — not jus...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/generate-tactics.md
What generate_tactics does on Freedom Mcp
AI agents use generate_tactics 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 |
|---|---|---|---|
lane_id | string | — | Optional lane UUID running these tactics (validated against this company). |
category | string | Yes | Growth category (4-F spine): flow=Leads, funnel=Conversion, flourish=LTV/retention, freedom=time/automation. |
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
userPrompt | string | Yes | The focus/request the tactics must address (e.g. "fill the top of funnel for our pharmacy ICP"). |
linked_kr_id | string | — | Optional key-result id (within the bound objective) the tactics most advance. |
objective_id | string | — | Optional OKR objective UUID to bind these tactics to (validated against this company). |
Parameters from the server's own tool schema.
Why generate_tactics is rated Medium
This tool creates new records in a business operations system (growth tactics) based on company strategy inputs. While it modifies state in the FreedomOS system, the changes are reversible (tactics can be updated, deleted, or archived). The approval gating indicates it's recognized as a mutation that may require authorization, but not a destructive or irreversible action.
From the tool's definition 'Generate AND save' tactics that 'Persist them as growth_tactics' — the tool creates and stores new data (growth tactics records).
Attacks that exploit this kind of access
The rule that runs generate_tactics 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 generate_tactics, this is the rule to start with:
generate_tactics 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 generate_tactics call is checked against it from then on.
Questions about generate_tactics
Generate AND save 5 grounded growth tactics for a 4-F category, composed from the company mission/vision, OKRs, and ICP customer profile. Persists them as growth_tactics (optionally bound to an objective, key result, and lane). Use when an agent should author concrete tactics for a goal — not just brainstorm. [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.
generate_tactics accepts 6 parameters: lane_id, category, companyId, userPrompt, linked_kr_id, objective_id. Required: category, companyId, userPrompt. 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 generate_tactics: 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.
generate_tactics 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 generate_tactics 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 generate_tactics. 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.
generate_tactics 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