get_tactics
List tactics for the company. Can filter by category or status.
This record as markdown: /tools/com-getfreedomos-freedom-mcp/get-tactics.md
What get_tactics does on Freedom Mcp
AI agents call get_tactics to retrieve information from Freedom Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Maximum number of tactics to return (default: 10) |
status | string | — | Filter by status |
category | string | — | Filter by category |
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
Parameters from the server's own tool schema.
Why get_tactics is rated Low
This is a read-only operation that queries and returns tactics data with optional filtering. It has no side effects, does not modify data, execute code, delete records, or move money. The blast radius if misused by an AI agent is minimal—it only exposes internal tactics information that would typically be readable to authorized users anyway.
From the tool's definition Tool name 'get_tactics' and description 'List tactics for the company. Can filter by category or status.' indicate a retrieval operation with no modification or execution of external actions.
Attacks that exploit this kind of access
The rule that runs get_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 get_tactics, this is the rule to start with:
get_tactics is read-only, so it stays allowed. 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 get_tactics call is checked against it from then on.
Questions about get_tactics
List tactics for the company. Can filter by category or status. It is categorised as a Read tool in the Freedom Mcp MCP Server, which means it retrieves data without modifying state.
get_tactics accepts 4 parameters: limit, status, category, companyId. 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 get_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.
get_tactics is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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