get_my_companies
List the companies the current operator can act in (their FreedomOS portfolio), with the operator's role in each plus an about line (entity type + what the company is/does). Call this to discover valid companyId values before using company-scoped tools, and use about — not the name — to infer WHI...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/get-my-companies.md
What get_my_companies does on Freedom Mcp
AI agents call get_my_companies 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 |
|---|---|---|---|
companyId | string | — | 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_my_companies is rated Low
This tool retrieves portfolio information about companies and the operator's roles. It performs no mutations, financial transfers, code execution, or irreversible actions. The purpose is to enumerate entities for subsequent tool invocation. The blast radius of misuse is minimal—an AI agent learning which companies exist in a portfolio and the operator's roles poses no immediate harm.
From the tool's definition Tool description explicitly states 'List the companies' and 'discover valid companyId values' — pure retrieval with no modification, deletion, or side effects.
Attacks that exploit this kind of access
The rule that runs get_my_companies 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_my_companies, this is the rule to start with:
get_my_companies 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_my_companies call is checked against it from then on.
Questions about get_my_companies
List the companies the current operator can act in (their FreedomOS portfolio), with the operator's role in each plus an about line (entity type + what the company is/does). Call this to discover valid companyId values before using company-scoped tools, and use about — not the name — to infer WHICH company the user means; if about doesn't settle it, ask rather than guess. It is categorised as a Read tool in the Freedom Mcp MCP Server, which means it retrieves data without modifying state.
get_my_companies accepts 1 parameter: 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_my_companies: 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_my_companies 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_my_companies 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_my_companies. 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_my_companies 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