brc_clear_audit_log

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

Critical RISK CLASS

Category Destructive

Parameters 30 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-bigredcloud-red-mcp-server/brc-clear-audit-log.md

WHAT IT DOES

What brc_clear_audit_log does on Red by Big Red Cloud

AI agents call brc_clear_audit_log to permanently remove resources in Red by Big Red Cloud, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Parameter	Type	Required	Description
`confirmClear`	boolean	—	Must be true to confirm that the session audit log should be cleared.
`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

Parameters from the server's own tool schema.

RISK

Why brc_clear_audit_log is rated Critical

An AI agent that decides to call brc_clear_audit_log doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Red by Big Red Cloud is gone. There is no undo for destructive operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

brc_clear_audit_log Hidden

brc_clear_audit_log is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "brc_clear_audit_log"
  ]
}

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

FAQ

Questions about brc_clear_audit_log

What does the brc_clear_audit_log tool do? +

Clear the Red audit log for this MCP server session. First call without confirmWrite: true returns confirmation_required and a payload preview — show a plain-English preview before posting in chat, then retry with confirmWrite: true only after explicit user confirmation in a later message. Red shows what it will post and waits for confirmation. Passing preflight is not confirmation. It is categorised as a Destructive tool in the Red by Big Red Cloud MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does brc_clear_audit_log accept? +

brc_clear_audit_log accepts 3 parameters: confirmClear, confirmWrite, connectionRef. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on brc_clear_audit_log? +

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

brc_clear_audit_log is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit brc_clear_audit_log? +

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

Set action: deny in the PolicyLayer policy for brc_clear_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_clear_audit_log? +

brc_clear_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 → Critical-risk tools on this server →

Across the catalogue

clear_renders on Why Did You Render →knowledge_clear on Templonix Lite MCP Server →clear_scan on Frida Game Hacking MCP →clear_spam_box on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →