brc_getting_started
Use this whenever the user asks how to start, says start or getting started, wants to connect or reconnect companies, or asks for a concise overview of Red. Return the current customer-friendly overview, connection steps, help options, safe workflow, and example prompts. For a specific tutorial, ...
This record as markdown: /tools/io-github-bigredcloud-red-mcp-server/brc-getting-started.md
What brc_getting_started does on Red by Big Red Cloud
AI agents invoke brc_getting_started 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.
Why brc_getting_started is rated High
brc_getting_started 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
The rule that runs brc_getting_started 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_getting_started, this is the rule to start with:
brc_getting_started 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Red by Big Red Cloud, apply this rule, and every brc_getting_started call is checked against it from then on.
Questions about brc_getting_started
Use this whenever the user asks how to start, says start or getting started, wants to connect or reconnect companies, or asks for a concise overview of Red. Return the current customer-friendly overview, connection steps, help options, safe workflow, and example prompts. For a specific tutorial, screenshot, article, YouTube video, or webinar question — or any red-help / /red-help command — use brc_red_help (or brc_find_help_resources for compatibility). If the user asks what they can do or what permissions they have, call brc_get_deployment_policy instead and state only current permissions — do not list tool names or counts. 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.
Register the Red by Big Red Cloud MCP server in PolicyLayer and add a rule for brc_getting_started: 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_getting_started is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the brc_getting_started 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_getting_started. 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_getting_started 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