request_connector

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

Medium RISK CLASS

Category Write

Parameters 32 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/request-connector.md

WHAT IT DOES

What request_connector does on Freedom Mcp

AI agents use request_connector to create or update resources in Freedom Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Freedom Mcp environment.

Parameter	Type	Required	Description
`reason`	string	—	Why you need it — the capability gap it closes (e.g. "run the KDP book ad campaign").
`companyId`	string	Yes	FreedomOS company id to act within (you must be a member). Required for company-scoped tools.
`connector`	string	Yes	Name of the connector to request (from search_connector_registry, e.g. "Amazon Ads").

Parameters from the server's own tool schema.

RISK

Why request_connector is rated Medium

This tool creates new records (approval cards, connector requests) and initiates multi-step processes that modify the system's integration configuration state. It does not retrieve data (Read), execute arbitrary external operations (Execute), delete data (Destructive), or move money (Financial).

From the tool's definition Tool description states it 'Creates a one-click approval card for the operator' and 'initiates a multi-step agent process' — these are state-creating actions.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

request_connector Rate-limited

request_connector stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "request_connector": {
      "limits": [
        {
          "counter": "request_connector_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 request_connector call is checked against it from then on.

FAQ

Questions about request_connector

What does the request_connector tool do? +

Request that the operator connect an external integration (MCP connector) so you can use its tools. Provide the connector name from search_connector_registry and a short reason for the capability gap it closes. Creates a one-click approval card for the operator. If the connector is NOT on the vetted allowlist, it becomes a "vet this connector" request instead. This does not connect anything by itself and never spends money. [sensitive-tier, initiates a multi-step agent process — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.]. It is categorised as a Write tool in the Freedom Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does request_connector accept? +

request_connector accepts 3 parameters: reason, companyId, connector. Required: companyId, connector. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on request_connector? +

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

request_connector is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit request_connector? +

Yes. Add a rate_limit block to the request_connector 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 request_connector completely? +

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

request_connector 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 →

Across the catalogue

http_request on 0sec → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →