brc_process_vat_category_rates

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

Low RISK CLASS

Category Read

Parameters 82 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-process-vat-category-rates.md

WHAT IT DOES

What brc_process_vat_category_rates does on Red by Big Red Cloud

AI agents call brc_process_vat_category_rates 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
`payload`	object	—	Deprecated. Use vatCategoryRates instead of a raw payload object.
`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
`effectiveDate`	string	—	Not a valid standalone payload. Use vatCategoryRates instead.
`confirmProcess`	boolean	—
`vatCategoryRates`	array	—	Full BRC payload array for POST /v1/vatCategories/vatRates, e.g. [{ vatCategoryId: 1, vatRates: [...] }].

Parameters from the server's own tool schema.

RISK

Why brc_process_vat_category_rates is rated Low

Even though brc_process_vat_category_rates 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.

Risk signalsAccepts raw HTML/template content (payload) · High parameter count (16 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

brc_process_vat_category_rates Allowed

brc_process_vat_category_rates is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "brc_process_vat_category_rates": {}
  }
}

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

FAQ

Questions about brc_process_vat_category_rates

What does the brc_process_vat_category_rates tool do? +

Processes VAT rates for VAT categories via POST /v1/vatCategories/vatRates. Requires a full vatCategoryRates array and confirmProcess=true. 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 Read tool in the Red by Big Red Cloud MCP Server, which means it retrieves data without modifying state.

What parameters does brc_process_vat_category_rates accept? +

brc_process_vat_category_rates accepts 8 parameters: payload, routeToken, companyName, confirmWrite, connectionRef, effectiveDate, confirmProcess, vatCategoryRates. Required: 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_process_vat_category_rates? +

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

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

Can I rate-limit brc_process_vat_category_rates? +

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

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

brc_process_vat_category_rates 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

get_cocktail_by_category on Cocktails RAG MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →