brc_route_request
MANDATORY FIRST STEP for Red requests that may create, update, delete, post, email, or batch-write company data. Classify and route a user request between Red's two main behaviours: action (perform the accounting workflow) and help (manual Big Red Cloud instructions). Also returns connection, rea...
This record as markdown: /tools/io-github-bigredcloud-red-mcp-server/brc-route-request.md
What brc_route_request does on Red by Big Red Cloud
AI agents call brc_route_request 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 |
|---|---|---|---|
message | string | Yes | The user's complete original message to classify, for example add a customer or how do I add a customer. |
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_route_request is rated Critical
An AI agent that decides to call brc_route_request 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.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs brc_route_request 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_route_request, this is the rule to start with:
brc_route_request 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_route_request call is checked against it from then on.
Questions about brc_route_request
MANDATORY FIRST STEP for Red requests that may create, update, delete, post, email, or batch-write company data. Classify and route a user request between Red's two main behaviours: action (perform the accounting workflow) and help (manual Big Red Cloud instructions). Also returns connection, read, unsupported_action, or unknown when those specialised modes apply. Pass the user's complete original message — never only a confirmation word such as yes or delete it when starting a new action. Action mode always returns a non-empty preferredTools list, allowedTools, and an opaque short-lived routeToken — pass that routeToken on every subsequent transactional tool call for the permitted workflow, including after lookup and preview. unsupported_action means Red cannot map the request to an enabled workflow — explain that to the user; do not invent a routeToken. Help mode runs the unified help search, returns manual resources, sets blockTransactionalTools true, and never issues a transactional routeToken. How-to wording (how do I, how can I, show me how, tell me how, where do I, what are the steps, manual steps for, red-help, /red-help) → mode help. Explicit action wording (add a customer, create a sales invoice, delete customer ABC, can you add a customer for me) → mode action with routeToken. A routeToken does not replace preview-before-posting or user confirmation (confirmWrite). Help mode does not persist — each brc_route_request call is classified independently unless returning confirmation continuation for a pending preview. Read-only classification and help search. Does not require a connected company. When a company is already connected, pass connectionRef silently so the routeToken can bind to that connection and survive MCP session rotation. 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_route_request accepts 2 parameters: message, connectionRef. Required: message. 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_route_request: 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_route_request 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_route_request 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_route_request. 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_route_request 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