brc_list_audit_log

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

Low RISK CLASS

Category Read

Parameters 20 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-list-audit-log.md

WHAT IT DOES

What brc_list_audit_log does on Red by Big Red Cloud

AI agents call brc_list_audit_log 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
`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
`includeTechnicalDetails`	boolean	—	Only set this to true if the user asks for technical details. Sensitive values are still redacted.

Parameters from the server's own tool schema.

RISK

Why brc_list_audit_log is rated Low

Even though brc_list_audit_log 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

RECOMMENDED RULE

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

brc_list_audit_log Allowed

brc_list_audit_log 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_list_audit_log": {}
  }
}

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

FAQ

Questions about brc_list_audit_log

What does the brc_list_audit_log tool do? +

Show a record of data changes (create, update, delete, batch, quote close/reopen, emails, etc.) made through this Red MCP server session. Read-only API calls are not logged. Use this as the source of truth for "what did I do today in Red?" style questions. When the user asks what they did "in Red" (or in Big Red Cloud), answer only from Red/BRC activity for the current Red session and for companies currently connected in this session: the Red/BRC audit log, BRC session actions, and connector-visible BRC activity. Never include activity from other MCP sessions, other users, other connections, or companies that are not currently connected (including ones that were disconnected or cleared). For "what did I do today/yesterday/last week in Red", only summarise current-session audit entries for currently connected companies; if older entries exist outside this scope, ignore them completely rather than reporting them. Do not include unrelated Claude chat history such as MCP debugging, Mistral debugging, coding work, or other non-BRC conversations unless the user explicitly asks for broader chat history. 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_list_audit_log accept? +

brc_list_audit_log accepts 2 parameters: connectionRef, includeTechnicalDetails. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on brc_list_audit_log? +

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

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

Can I rate-limit brc_list_audit_log? +

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

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

brc_list_audit_log 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

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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