run_tactic

SERVERFreedom Mcp SOURCEhttps://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp

High RISK CLASS

Category Execute

Parameters 51 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-getfreedomos-freedom-mcp/run-tactic.md

WHAT IT DOES

What run_tactic does on Freedom Mcp

AI agents invoke run_tactic 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
`companyId`	string	Yes	FreedomOS company id to act within (you must be a member). Required for company-scoped tools.
`tactic_id`	string	—	UUID of the Play/tactic to run (use this or tactic_title).
`agent_name`	string	—	Optional: override which agent runs it (else resolved from the tactic's lane or assignee).
`suggest_only`	boolean	—	If true, return Play execution brief only (who / steps / readiness / estimate) — no dispatch, no spend, no Agree required. Use for Chat/MCP dry-run before Run.
`tactic_title`	string	—	Title (or fragment) of the Play/tactic to run (use this or tactic_id).

Parameters from the server's own tool schema.

RISK

Why run_tactic is rated High

This tool's core function is to trigger execution of saved business plays and dispatch agent activities. While it can preview without spend via suggest_only, the primary purpose is to initiate multi-step processes that execute business tactics. This is Execute category because it runs external operations whose effects depend on which play is selected and executed.

From the tool's definition "Run a saved Play (growth_tactics) for the company operator or agent — dispatch the next unit as a one-off draft activity" and "preview cast/steps/cost without spend" and "initiates a multi-step agent process" indicate triggering external operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_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 run_tactic, this is the rule to start with:

run_tactic Rate-limited

run_tactic 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_tactic": {
      "limits": [
        {
          "counter": "run_tactic_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Freedom Mcp, apply this rule, and every run_tactic call is checked against it from then on.

FAQ

Questions about run_tactic

What does the run_tactic tool do? +

Run a saved Play (growth_tactics) for the company operator or agent — dispatch the next unit as a one-off draft activity, or dry-run a Play brief with suggest_only. Use when the operator or agent should execute an Agreed play this cycle (same owner as Focus “Run play”), or preview cast/steps/cost without spend. Structured plays require plan Agree before dispatch; suggest_only does not. [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.

What parameters does run_tactic accept? +

run_tactic accepts 5 parameters: companyId, tactic_id, agent_name, suggest_only, tactic_title. Required: companyId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on run_tactic? +

Register the Freedom MCP server in PolicyLayer and add a rule for run_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.

What risk level is run_tactic? +

run_tactic is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_tactic? +

Yes. Add a rate_limit block to the run_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.

How do I block run_tactic completely? +

Set action: deny in the PolicyLayer policy for run_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.

What MCP server provides run_tactic? +

run_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.

KEEP EXPLORING

More on Freedom, and thousands of servers like it.

This server

All 238 Freedom tools → High-risk tools on this server →

Across the catalogue

run on 0sec →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →