brc_update_sales_entry

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

Medium RISK CLASS

Category Write

Parameters 73 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-update-sales-entry.md

WHAT IT DOES

What brc_update_sales_entry does on Red by Big Red Cloud

AI agents use brc_update_sales_entry to create or update resources in Red by Big Red Cloud, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Red by Big Red Cloud environment.

Parameter	Type	Required	Description
`id`	object	Yes	Sales entry id.
`note`	string	—	Optional. BRC "Note" field on the sales document (JSON field `note`). Leave blank to default it to the customer name (BRC customer "Name" / JSON `name`). Do not
`reference`	string	—	Optional. BRC "Reference" field (JSON field `reference`). BRC "Our Ref" (JSON `ourReference`) and BRC "Your Ref" (JSON `yourReference`) default to this value wh
`routeToken`	string	Yes	Opaque routeToken from brc_route_request for this action workflow. Required for transactional tools. Routing permission only — does not replace preview-before-p
`companyName`	string	Yes	Company context name, for example YOUR-COMPANY-NAME.
`confirmWrite`	boolean	—	Must be true only after a plain-English preview before posting has been shown in the current conversation and the user explicitly confirmed posting (for example
`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_update_sales_entry is rated Medium

An AI agent can call brc_update_sales_entry faster than any human can review: one bad instruction and it creates or modifies resources in Red by Big Red Cloud by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

brc_update_sales_entry Rate-limited

brc_update_sales_entry stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_update_sales_entry": {
      "limits": [
        {
          "counter": "brc_update_sales_entry_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

FAQ

Questions about brc_update_sales_entry

What does the brc_update_sales_entry tool do? +

Updates a BRC sales entry using structured safe text/reference fields. Requires routeToken from brc_route_request for the matching action workflow. Call brc_route_request first with the user's complete original action request. Retain the returned routeToken through lookup, preview, and confirmation, and pass the same token on the final permitted transactional tool call. Never invent a placeholder token. A routeToken is not permission to post — preview-before-posting and confirmWrite/confirmDelete still apply. It is categorised as a Write tool in the Red by Big Red Cloud MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does brc_update_sales_entry accept? +

brc_update_sales_entry accepts 7 parameters: id, note, reference, routeToken, companyName, confirmWrite, connectionRef. Required: id, routeToken, companyName. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on brc_update_sales_entry? +

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

brc_update_sales_entry is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit brc_update_sales_entry? +

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

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

brc_update_sales_entry 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

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →