list_audit_events

SERVERBusymate DevTools SOURCEhttps://mcp.busymate.dev

Low RISK CLASS

Category Read

Parameters 120 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-busymate-busymate-devtools/list-audit-events.md

WHAT IT DOES

What list_audit_events does on Busymate DevTools

AI agents call list_audit_events 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
`q`	string	—	Free-text substring across action/actor_label/target_label/actor_id/target_id/surface/db_session_user.
`all`	boolean	—	audit:view operators only — read EVERY actor's events (the fleet trail) instead of just YOUR OWN.
`asc`	boolean	—	Oldest-first (default false = newest-first).
`limit`	number	—	Max rows (default 100, cap 500).
`since`	string	—	ISO timestamp — window start (default 24h ago; clamped to ≥ 90 days ago).
`until`	string	—	ISO timestamp — window end (default now).
`status`	string	—	Exact status filter (ok\|denied\|error\|timeout).
`actor_q`	string	—	Substring match on actor_label or actor_id.
`surface`	string	—	Exact surface filter (mcp\|busybro\|dashboard\|rest\|db\|auth\|proxy\|daemon\|cron\|ios\|cdp\|farm\|edge:<fn>).
`action_q`	string	—	Substring match on the action (tool name / route / db:op:table).
`actor_id`	string	—	Exact actor id (OAuth sub / device uuid / db role). A FOREIGN actor requires audit:view (all:true).
`target_q`	string	—	Substring match on target_label/target_id/target_kind.

Parameters from the server's own tool schema.

RISK

Why list_audit_events is rated Low

This tool retrieves audit trail data without modifying, executing code, deleting, or moving money. It is a pure Read operation. Severity is medium rather than low because audit logs can reveal sensitive operational details, user behavior patterns, and system configuration that could inform further attacks, though the data is scoped to the caller's own events, which mitigates exposure somewhat.

From the tool's definition Tool name is 'list_audit_events' with description stating 'Read the platform AUDIT TRAIL (public.audit_log)' — explicitly a read operation that retrieves audit log data.

Risk signalsHigh parameter count (18 properties) · Bulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_audit_events Allowed

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

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

FAQ

Questions about list_audit_events

What does the list_audit_events tool do? +

Read the platform AUDIT TRAIL (public.audit_log) — the unified who-did-what-when-how ledger across every surface (mcp / busybro / dashboard / rest / db / auth / proxy / daemon / cron / ios / cdp / farm / edge:<fn> — #533: the surface is DERIVED at the DB trigger tier by HOW a write ARRIVED — a direct-Postgres write→db (the tamper class, also flagged by is_direct_pg), a device PostgREST write→ios/cdp/farm/rest by its platform, a dashboard PostgREST write→dashboard, a plain REST write→rest). YOUR OWN events by default (owner-scoped to the calling account's actor_id — the same reach the /audit page gives you), or the WHOLE FLEET with all:true (audit:view operators only; re-verified server-side, fail-closed — for a non-operator all is rejected, never silently widened). Each row is a SLIM projection (no detail/statement_excerpt — fetch those with get_audit_event): id, at, actor_kind (user|service|device|webhook|anon|system), actor_id + actor_label (the human name snapshot), client_id, jti, actor_ip, user_agent, db_session_user, is_direct_pg (a DIRECT-Postgres write — the #026 tamper signature), surface, action, target_kind/target_id/target_label, device_uuid, rows_changed, status (ok|denied|error|timeout), method, latency_ms, request_id (correlate one action across layers). MANDATORY time window: since/until (ISO; since defaults to 24h ago, clamped to ≥ 90 days ago — the retention horizon). Filters: surface, status, actor_id (exact — operators only for a foreign actor), actor_q/action_q/target_q (per-field substring), target_kind+target_id (exact — the history deep-link), request_id, direct_only:true (only direct-PG writes), q (free-text multi-column substring across action/actor/target/surface). KEYSET pagination: pass the returned next_cursor {before_at, before_id} to page further; asc:true for oldest-first; limit (default 100, cap 500). detail is REDACTED at write time (never raw args/secrets). Returns { ok, scope: own|fleet, count, next_cursor, events:[…] }. It is categorised as a Read tool in the Busymate DevTools MCP Server, which means it retrieves data without modifying state.

What parameters does list_audit_events accept? +

list_audit_events accepts 12 parameters: q, all, asc, limit, since, until, status, actor_q, surface, action_q, actor_id, target_q. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_audit_events? +

Register the Busymate DevTools MCP server in PolicyLayer and add a rule for list_audit_events: 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 list_audit_events? +

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

Can I rate-limit list_audit_events? +

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

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

list_audit_events 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

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

Guides

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