brc_validate_transaction_date
Checks whether a proposed transaction date is inside the connected BRC company's current financial year.
This record as markdown: /tools/io-github-bigredcloud-red-mcp-server/brc-validate-transaction-date.md
What brc_validate_transaction_date does on Red by Big Red Cloud
AI agents call brc_validate_transaction_date 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
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 |
transactionDate | string | Yes | Date to validate in YYYY-MM-DD format. |
Parameters from the server's own tool schema.
Why brc_validate_transaction_date is rated Low
Even though brc_validate_transaction_date 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.
Attacks that exploit this kind of access
The rule that runs brc_validate_transaction_date 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_validate_transaction_date, this is the rule to start with:
brc_validate_transaction_date is read-only, so it stays allowed. 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_validate_transaction_date call is checked against it from then on.
Questions about brc_validate_transaction_date
Checks whether a proposed transaction date is inside the connected BRC company's current financial year. It is categorised as a Read tool in the Red by Big Red Cloud MCP Server, which means it retrieves data without modifying state.
brc_validate_transaction_date accepts 3 parameters: companyName, connectionRef, transactionDate. Required: companyName, transactionDate. 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_validate_transaction_date: 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_validate_transaction_date is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the brc_validate_transaction_date 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_validate_transaction_date. 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_validate_transaction_date 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.
This server
Across the catalogue