delete_tactic
Archive a tactic (safe delete - recoverable). Can identify by title instead of 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.]
This record as markdown: /tools/com-getfreedomos-freedom-mcp/delete-tactic.md
What delete_tactic does on Freedom Mcp
AI agents use delete_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 |
|---|---|---|---|
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 archive (optional if using tactic_title) |
tactic_title | string | — | Title of the tactic to archive (use this or tactic_id) |
Parameters from the server's own tool schema.
Why delete_tactic is rated Medium
Archives/soft-deletes a tactic but is explicitly recoverable, making it a reversible Write action.
From the tool's definition Archive a tactic (safe delete - recoverable)
Attacks that exploit this kind of access
The rule that runs delete_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 delete_tactic, this is the rule to start with:
delete_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 delete_tactic call is checked against it from then on.
Questions about delete_tactic
Archive a tactic (safe delete - recoverable). Can identify by title instead of 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.
delete_tactic accepts 3 parameters: companyId, tactic_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 delete_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.
delete_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 delete_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 delete_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.
delete_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