search_connector_registry

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

Low RISK CLASS

Category Read

Parameters 21 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-getfreedomos-freedom-mcp/search-connector-registry.md

WHAT IT DOES

What search_connector_registry does on Freedom Mcp

AI agents call search_connector_registry 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
`query`	string	—	Optional keyword to filter by name or capability (e.g. "ads", "amazon", "analytics"). Omit to list the whole vetted catalog.
`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.

RISK

Why search_connector_registry is rated Low

This tool retrieves information from a pre-vetted registry of available connectors. It has no side effects—it does not create, modify, delete, or execute anything. It is a pure search/lookup function. The subsequent action (calling 'request_connector') is a separate step, meaning this tool itself only reads and returns metadata about available integrations.

From the tool's definition Tool name is 'search_connector_registry' and description states it 'Search[es] the vetted connector registry' and 'Returns' results. The verb 'search' and 'returns' indicate data retrieval only.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

search_connector_registry Allowed

search_connector_registry is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_connector_registry": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about search_connector_registry

What does the search_connector_registry tool do? +

Search the vetted connector registry for an external integration (MCP connector) you need but that is not yet connected. Returns ONLY FreedomOS-allowlisted connectors (e.g. ad platforms, analytics) — never the open internet. Use this when you hit a capability gap, then call request_connector with the name to ask the operator to connect one. It is categorised as a Read tool in the Freedom Mcp MCP Server, which means it retrieves data without modifying state.

What parameters does search_connector_registry accept? +

search_connector_registry accepts 2 parameters: query, companyId. Required: companyId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on search_connector_registry? +

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

search_connector_registry is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_connector_registry? +

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

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

search_connector_registry 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

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →