brc_list_company_contexts

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

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What brc_list_company_contexts does on Red by Big Red Cloud

AI agents call brc_list_company_contexts to retrieve information from Red by Big Red Cloud 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
`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_list_company_contexts is rated Low

Even though brc_list_company_contexts only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

brc_list_company_contexts Allowed

brc_list_company_contexts 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": {
    "brc_list_company_contexts": {}
  }
}

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

FAQ

Questions about brc_list_company_contexts

What does the brc_list_company_contexts tool do? +

Lists company contexts currently connected in this MCP server session. Use this when the user asks which companies are connected, how long the connection lasts, how much time is left, when companies disconnect, when the session expires, or what timezone the expiry is in. Present the result to the user with the customerMessage text, company names, and expiryMessage when connected. Answer duration and time-left questions using connectionDurationText, timeRemainingText, expiryTimeWithTimezoneText, expiryTimezoneName, expiryTimezoneAbbreviation, expiryUtcOffset, and expiryMessage from the response — do not say you do not know the current time or that you lack a live clock when timeRemainingText is present. Do not ask the user to check their device clock. Do not say local time on its own. Customer duration answers should explain how long the connection lasts, that a fresh secure link is needed after expiry, and that the one-time connection link itself cannot be reused. Do not mention authentication classifications, empty-result logic, connectionRef, rehydration, HTTP status codes, session bindings, or other internal diagnostics in customer answers. Do not show connectionRef, activeConnectionRef, redconn_ values, session IDs, or diagnostic metadata to normal users. Do not show raw ISO expiresAt or credentialType to normal users unless they specifically ask or dev mode is enabled. Connection credentials are never returned. If you have connectionRef from brc_confirm_company_connection, pass it silently on this call when the MCP client rotates session ids. An empty list with a working connectionRef means no companies are bound yet — not a reason to start a new connection if other tools already succeeded with the same connectionRef. It is categorised as a Read tool in the Red by Big Red Cloud MCP Server, which means it retrieves data without modifying state.

What parameters does brc_list_company_contexts accept? +

brc_list_company_contexts 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_list_company_contexts? +

Register the Red by Big Red Cloud MCP server in PolicyLayer and add a rule for brc_list_company_contexts: 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_list_company_contexts? +

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

Can I rate-limit brc_list_company_contexts? +

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

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

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

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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