get_routing_overview
See how agent output is currently routed — who is responsible for which domains in the company.
This record as markdown: /tools/com-getfreedomos-freedom-mcp/get-routing-overview.md
What get_routing_overview does on Freedom Mcp
AI agents call get_routing_overview 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 | 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_routing_overview is rated Low
This tool retrieves and displays current routing information (responsibility mappings by domain) with no side effects. It is purely informational, allowing inspection of existing organizational structure. No data is created, modified, deleted, or executed. This is a straightforward Read category tool with low severity since viewing routing metadata poses minimal risk even if misused by an agent.
From the tool's definition Tool description states "See how agent output is currently routed" — a retrieval/query operation that exposes organizational routing configuration without modifying it.
Attacks that exploit this kind of access
The rule that runs get_routing_overview 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_routing_overview, this is the rule to start with:
get_routing_overview 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_routing_overview call is checked against it from then on.
Questions about get_routing_overview
See how agent output is currently routed — who is responsible for which domains in the company. It is categorised as a Read tool in the Freedom Mcp MCP Server, which means it retrieves data without modifying state.
get_routing_overview accepts 1 parameter: 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_routing_overview: 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_routing_overview 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_routing_overview 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_routing_overview. 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_routing_overview 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