invoke_integration

SERVERFreedom Mcp SOURCEhttps://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp

High RISK CLASS

Category Execute

Parameters 43 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-getfreedomos-freedom-mcp/invoke-integration.md

WHAT IT DOES

What invoke_integration does on Freedom Mcp

AI agents invoke invoke_integration to trigger actions in Freedom Mcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`arguments`	object	—	Arguments to pass to the tool
`companyId`	string	Yes	FreedomOS company id to act within (you must be a member). Required for company-scoped tools.
`tool_name`	string	Yes	Name of the tool to execute on the integration
`integration_name`	string	Yes	Name of the integration (e.g., "stripe", "calendar")

Parameters from the server's own tool schema.

RISK

Why invoke_integration is rated High

This tool runs code or operations on external systems via connected integrations. The outcome is not predetermined; it depends entirely on which integration is invoked and what parameters are supplied. While the approval requirement (human rail on every call) is a strong mitigating control, the tool itself has Execute semantics and wide blast radius if approval is bypassed or misconfigured.

From the tool's definition Tool description states 'Execute a tool on a connected MCP integration' — the word 'Execute' is explicit. The tool invokes arbitrary external integrations whose behavior depends on arguments (which integration and parameters are passed).

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs invoke_integration 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 invoke_integration, this is the rule to start with:

invoke_integration Rate-limited

invoke_integration stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "invoke_integration": {
      "limits": [
        {
          "counter": "invoke_integration_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Freedom Mcp, apply this rule, and every invoke_integration call is checked against it from then on.

FAQ

Questions about invoke_integration

What does the invoke_integration tool do? +

Execute a tool on a connected MCP integration. First use list_integrations to discover available tools. [outbound-tier — EVERY call needs a manager's approval (per-send human rail): each request queues its own approval card and sends exactly once on approve. There is no standing grant for this tool.]. It is categorised as a Execute tool in the Freedom Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does invoke_integration accept? +

invoke_integration accepts 4 parameters: arguments, companyId, tool_name, integration_name. Required: companyId, tool_name, integration_name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on invoke_integration? +

Register the Freedom MCP server in PolicyLayer and add a rule for invoke_integration: 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.

What risk level is invoke_integration? +

invoke_integration is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit invoke_integration? +

Yes. Add a rate_limit block to the invoke_integration 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.

How do I block invoke_integration completely? +

Set action: deny in the PolicyLayer policy for invoke_integration. 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.

What MCP server provides invoke_integration? +

invoke_integration 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.

KEEP EXPLORING

More on Freedom, and thousands of servers like it.

This server

All 238 Freedom tools → High-risk tools on this server →

Across the catalogue

qt_invoke_slot on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →