brc_create_nominal_journal_batch
Creates a new Nominal Journal Batch. The journal should contain balanced debit and credit lines. Do not call with confirmWrite=true until the user has reviewed the preview and explicitly confirmed creation. Requires routeToken from brc_route_request for the matching action workflow. Call brc_rout...
This record as markdown: /tools/io-github-bigredcloud-red-mcp-server/brc-create-nominal-journal-batch.md
What brc_create_nominal_journal_batch does on Red by Big Red Cloud
AI agents use brc_create_nominal_journal_batch 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 |
|---|---|---|---|
total | number | Yes | Total journal amount. |
procDate | string | Yes | Processing date, for example 2024-01-15T00:00:00. |
entryDate | string | Yes | Entry date, for example 2024-01-15T00:00:00. |
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 the user explicitly confirms creating this Nominal Journal Batch. |
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 |
bookTranTypeId | integer | — | Book transaction type id. Nominal Journal Batch is usually 7. |
accountTransactions | array | Yes | Nominal journal account transaction lines. Debits and credits should balance. |
Parameters from the server's own tool schema.
Why brc_create_nominal_journal_batch is rated Medium
An AI agent can call brc_create_nominal_journal_batch 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.
Risk signalsHigh parameter count (17 properties)
Attacks that exploit this kind of access
The rule that runs brc_create_nominal_journal_batch 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_create_nominal_journal_batch, this is the rule to start with:
brc_create_nominal_journal_batch 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Red by Big Red Cloud, apply this rule, and every brc_create_nominal_journal_batch call is checked against it from then on.
Questions about brc_create_nominal_journal_batch
Creates a new Nominal Journal Batch. The journal should contain balanced debit and credit lines. Do not call with confirmWrite=true until the user has reviewed the preview and explicitly confirmed creation. 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.
brc_create_nominal_journal_batch accepts 9 parameters: total, procDate, entryDate, routeToken, companyName, confirmWrite, connectionRef, bookTranTypeId, accountTransactions. Required: total, procDate, entryDate, routeToken, companyName, accountTransactions. 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_create_nominal_journal_batch: 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_create_nominal_journal_batch is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the brc_create_nominal_journal_batch 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_create_nominal_journal_batch. 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_create_nominal_journal_batch 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