New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

brc_check_transaction_settings

Checks BRC company processing settings before a VAT-sensitive or payment-terms-sensitive transaction workflow. Returns warnings that should be shown before creating or changing records. Use this for one workflow (sales invoice, purchase, cash receipt, or statement). For overall company readiness ...

SERVERRed by Big Red Cloud SOURCEhttps://red.bigredcloud.com/mcp
Low RISK CLASS
Category Read
Parameters 32 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-bigredcloud-red-mcp-server/brc-check-transaction-settings.md

What brc_check_transaction_settings does on Red by Big Red Cloud

AI agents call brc_check_transaction_settings to retrieve information from Red by Big Red Cloud without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
workflow string Yes The workflow to check against the company processing settings.
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_check_transaction_settings is rated Low

Even though brc_check_transaction_settings only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Questions about brc_check_transaction_settings

What does the brc_check_transaction_settings tool do? +

Checks BRC company processing settings before a VAT-sensitive or payment-terms-sensitive transaction workflow. Returns warnings that should be shown before creating or changing records. Use this for one workflow (sales invoice, purchase, cash receipt, or statement). For overall company readiness (connection, financial year, Sales VAT, Sales Analysis, reference data), use brc_company_readiness_check instead. It is categorised as a Read tool in the Red by Big Red Cloud MCP Server, which means it retrieves data without modifying state.

What parameters does brc_check_transaction_settings accept? +

brc_check_transaction_settings accepts 3 parameters: workflow, companyName, connectionRef. Required: workflow, companyName. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on brc_check_transaction_settings? +

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

brc_check_transaction_settings is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit brc_check_transaction_settings? +

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

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

brc_check_transaction_settings 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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Red by Big Red Cloud's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.