get_audit_event

SERVERBusymate DevTools SOURCEhttps://mcp.busymate.dev

Low RISK CLASS

Category Read

Parameters 21 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-busymate-busymate-devtools/get-audit-event.md

WHAT IT DOES

What get_audit_event does on Busymate DevTools

AI agents call get_audit_event to retrieve information from Busymate DevTools 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
`at`	string	—	The row's `at` timestamp (ISO, from list_audit_events) — partition-prune hint.
`id`	number	Yes	The audit_log row id (from list_audit_events).

Parameters from the server's own tool schema.

RISK

Why get_audit_event is rated Low

This is fundamentally a read/query operation that retrieves audit log entries. It has no side effects and performs no writes, deletes, or state changes. However, severity is high because: (1) audit logs typically contain sensitive system activity and security-relevant information; (2) the tool returns 'detail' fields including diffs and SQL statements that could expose system internals; (3) access is scoped by user…

From the tool's definition Tool performs 'Get ONE audit-trail row in FULL by its id' with 'detail (old→new diffs for allowlisted keys, redacted at write time)' and 'statement_excerpt (the left-400-char SQL)'.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_audit_event safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Busymate DevTools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_audit_event, this is the rule to start with:

get_audit_event Allowed

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Busymate DevTools, apply this rule, and every get_audit_event call is checked against it from then on.

FAQ

Questions about get_audit_event

What does the get_audit_event tool do? +

Get ONE audit-trail row in FULL by its id (from list_audit_events) — including the fields the list omits: the REDACTED detail (old→new diffs for allowlisted keys, redacted at write time — never raw args/secrets) and statement_excerpt (the left-400-char SQL for a direct-PG write). Owner-scoped: a row whose actor isn't YOU returns not-found (found:false) unless you hold audit:view (operators can read any row) — an out-of-reach row is never distinguished from a non-existent one. Pass at (the row's timestamp from the list) to prune the partition for a faster lookup. Returns { ok, found, event }. It is categorised as a Read tool in the Busymate DevTools MCP Server, which means it retrieves data without modifying state.

What parameters does get_audit_event accept? +

get_audit_event accepts 2 parameters: at, id. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_audit_event? +

Register the Busymate DevTools MCP server in PolicyLayer and add a rule for get_audit_event: 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 Busymate DevTools. Nothing to install.

What risk level is get_audit_event? +

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

Can I rate-limit get_audit_event? +

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

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

get_audit_event is provided by the Busymate DevTools MCP server (https://mcp.busymate.dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Busymate DevTools, and thousands of servers like it.

This server

All 44 Busymate DevTools tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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