brc_start_company_connection

SERVERRed by Big Red Cloud SOURCEhttps://red.bigredcloud.com/mcp

High RISK CLASS

Category Execute

Parameters 10 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-bigredcloud-red-mcp-server/brc-start-company-connection.md

WHAT IT DOES

What brc_start_company_connection does on Red by Big Red Cloud

AI agents invoke brc_start_company_connection to trigger actions in Red by Big Red Cloud. 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
`connectionRef`	string	—	Opaque Red connection reference returned by brc_confirm_company_connection. Pass this exact value on every later tool call when the MCP client rotates session i

Parameters from the server's own tool schema.

RISK

Why brc_start_company_connection is rated High

brc_start_company_connection triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs brc_start_company_connection safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Red by Big Red Cloud, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For brc_start_company_connection, this is the rule to start with:

brc_start_company_connection Rate-limited

brc_start_company_connection 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": {
    "brc_start_company_connection": {
      "limits": [
        {
          "counter": "brc_start_company_connection_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 Red by Big Red Cloud, apply this rule, and every brc_start_company_connection call is checked against it from then on.

FAQ

Questions about brc_start_company_connection

What does the brc_start_company_connection tool do? +

Starts the secure Red company connection flow and generates a fresh one-time secure Red connection link and confirmation code. Use only when there is no active company connection, no valid connectionRef, the user explicitly asks to connect or reconnect, try again after a failed connection, expired session credentials, or when an old, used, or stale secure connection link no longer works. Do not call this tool when a valid connectionRef from brc_confirm_company_connection is already available and recent tool calls succeeded with it. Do not call this tool because a lookup returned no rows, partial data, or an empty list — that means no matching records, not an expired connection. Do not call this tool after successful company data retrieval unless the user explicitly asks to connect, reconnect, or add more companies. Always call this tool again to generate a new link — never reuse a previous connection link. Returns a one-time connection page URL (no time expiry, but each link works only once). On that page the user can enter a single company or upload a CSV for multiple companies — never in chat. After completing the secure page, the user should return to this chat and provide (copy/paste) the confirmation code shown on the success page. Do not paste an API key into chat. It is categorised as a Execute tool in the Red by Big Red Cloud MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does brc_start_company_connection accept? +

brc_start_company_connection accepts 1 parameter: connectionRef. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on brc_start_company_connection? +

Register the Red by Big Red Cloud MCP server in PolicyLayer and add a rule for brc_start_company_connection: 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 Red by Big Red Cloud. Nothing to install.

What risk level is brc_start_company_connection? +

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

Can I rate-limit brc_start_company_connection? +

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

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

brc_start_company_connection is provided by the Red by Big Red Cloud MCP server (https://red.bigredcloud.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Red by Big Red Cloud, and thousands of servers like it.

This server

All 159 Red by Big Red Cloud tools → High-risk tools on this server →

Across the catalogue

start_devtools_monitoring on Percepta MCP Server →team_manager_start_room on Team Manager MCP →start_etw_trace on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

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