brc_delete_cash_receipt

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

Critical RISK CLASS

Category Destructive

Parameters 63 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-bigredcloud-red-mcp-server/brc-delete-cash-receipt.md

WHAT IT DOES

What brc_delete_cash_receipt does on Red by Big Red Cloud

AI agents call brc_delete_cash_receipt 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
`id`	object	Yes	cash receipt id.
`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
`confirmDelete`	boolean	—
`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_delete_cash_receipt is rated Critical

An AI agent that decides to call brc_delete_cash_receipt 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

RECOMMENDED RULE

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

brc_delete_cash_receipt Hidden

brc_delete_cash_receipt is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "brc_delete_cash_receipt"
  ]
}

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

FAQ

Questions about brc_delete_cash_receipt

What does the brc_delete_cash_receipt tool do? +

Deletes a BRC cash receipt by id. 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 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.

What parameters does brc_delete_cash_receipt accept? +

brc_delete_cash_receipt accepts 6 parameters: id, routeToken, companyName, confirmWrite, confirmDelete, 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_delete_cash_receipt? +

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

brc_delete_cash_receipt is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit brc_delete_cash_receipt? +

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

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

brc_delete_cash_receipt 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 → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →