list_integrations
List ALL connected external integrations — MCP servers, OAuth accounts (Google, X, ...), and direct integrations (Xero accounting, Stripe) — and the tools each one powers. Use when user asks about connected services, integrations, or what external tools are available.
This record as markdown: /tools/com-getfreedomos-freedom-mcp/list-integrations.md
What list_integrations does on Freedom Mcp
AI agents call list_integrations 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. |
include_tools | boolean | — | Include list of available tools for each integration (default: true) |
Parameters from the server's own tool schema.
Why list_integrations is rated Low
This tool retrieves and enumerates metadata about connected integrations (MCP servers, OAuth accounts, Stripe, Xero, etc.) and the tools they power. It is a pure read operation—querying and displaying configuration information.
From the tool's definition Tool name and description: 'List ALL connected external integrations' and 'Use when user asks about connected services, integrations, or what external tools are available.' The verb is 'list', a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs list_integrations 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 list_integrations, this is the rule to start with:
list_integrations 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 list_integrations call is checked against it from then on.
Questions about list_integrations
List ALL connected external integrations — MCP servers, OAuth accounts (Google, X, ...), and direct integrations (Xero accounting, Stripe) — and the tools each one powers. Use when user asks about connected services, integrations, or what external tools are available. It is categorised as a Read tool in the Freedom Mcp MCP Server, which means it retrieves data without modifying state.
list_integrations accepts 2 parameters: companyId, include_tools. 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 list_integrations: 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.
list_integrations 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 list_integrations 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 list_integrations. 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.
list_integrations 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