get_okrs
List objectives and key results for the company. Defaults to current year unless year specified or all_years=true.
This record as markdown: /tools/com-getfreedomos-freedom-mcp/get-okrs.md
What get_okrs does on Freedom Mcp
AI agents call get_okrs 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 |
|---|---|---|---|
year | number | — | Filter by year (e.g., 2026). Defaults to current year. |
limit | number | — | Maximum number to return (default: 10) |
all_years | boolean | — | Set to true to get OKRs across all years (overrides year filter) |
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_okrs is rated Low
This tool queries and retrieves OKR data without creating, modifying, deleting, or executing operations. It has no side effects beyond fetching information. While OKRs may be business-sensitive, the tool itself performs only read access, making it low severity with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'get_okrs' and description 'List objectives and key results' indicates data retrieval with no modification. Verb 'List' is explicitly a read operation.
Attacks that exploit this kind of access
The rule that runs get_okrs 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_okrs, this is the rule to start with:
get_okrs 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_okrs call is checked against it from then on.
Questions about get_okrs
List objectives and key results for the company. Defaults to current year unless year specified or all_years=true. It is categorised as a Read tool in the Freedom Mcp MCP Server, which means it retrieves data without modifying state.
get_okrs accepts 4 parameters: year, limit, all_years, 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_okrs: 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_okrs 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_okrs 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_okrs. 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_okrs 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