brc_clear_company_api_key
Clears the API key for a named company context from MCP server memory.
This record as markdown: /tools/io-github-bigredcloud-red-mcp-server/brc-clear-company-api-key.md
What brc_clear_company_api_key does on Red by Big Red Cloud
AI agents call brc_clear_company_api_key to permanently remove resources in Red by Big Red Cloud, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
companyName | string | Yes | Company context name, for example YOUR-COMPANY-NAME. |
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.
Why brc_clear_company_api_key is rated Critical
An AI agent that decides to call brc_clear_company_api_key doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Red by Big Red Cloud is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs brc_clear_company_api_key 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_clear_company_api_key, this is the rule to start with:
brc_clear_company_api_key is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Red by Big Red Cloud, apply this rule, and every brc_clear_company_api_key call is checked against it from then on.
Questions about brc_clear_company_api_key
Clears the API key for a named company context from MCP server memory. It is categorised as a Destructive tool in the Red by Big Red Cloud MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
brc_clear_company_api_key accepts 2 parameters: companyName, connectionRef. Required: companyName. The full parameter table on this page comes from the server's own tool schema.
Register the Red by Big Red Cloud MCP server in PolicyLayer and add a rule for brc_clear_company_api_key: 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.
brc_clear_company_api_key is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the brc_clear_company_api_key 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.
Set action: deny in the PolicyLayer policy for brc_clear_company_api_key. 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.
brc_clear_company_api_key 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.
More on Red by Big Red Cloud, and thousands of servers like it.
Across the catalogue