// SCAN REPORT

Audit event mcp

6 tools. 2 can modify or destroy data without limits.

2 write tools that can modify data. Rate limits recommended.

Last updated: 30 Jun 2026

2 can modify or destroy data

4 read-only

6 tools total

Community server · catalogue entry verified 30/06/2026

How to control Audit event mcp ↓

TOOL MAP

What Audit event mcp exposes to your agents

Read (4) Write / Execute (2) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Audit event mcp tools

Write · Medium record_event This tool creates new data (audit events) in a hash-chained log, which is reversible in principle (entries could be archived or marked as superseded). Write · Medium request_approval This tool creates a new approval record and logs a chain event — a reversible write operation.

2 of Audit event mcp's 6 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Audit event mcp

PolicyLayer is an MCP gateway — it sits between your AI agents and Audit event mcp, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "record_event": {
    "limits": [
      {
        "counter": "record_event_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "check_approval": {
    "limits": [
      {
        "counter": "check_approval_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Audit event mcp — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON AUDIT EVENT →

Instant setup, no code required.

FULL CATALOGUE

All 6 Audit event mcp tools

WRITE 2 tools

Write record_event Write one audit event to the hash-chained log. Returns the event id and chain_hash. Write request_approval Ask a human to approve an action before it runs. Creates a pending approval, witnesses it as an approval.reque

READ 4 tools

Read check_approval Poll an approval Read export_dossier Export all events for a subject_id as a signed JSON-L file (GDPR Art. 20 portability). Returns an R2 presigned Read query_events Filter events by session_id, event_type, agent_id, or date range. Returns paginated events. input_hash is neve Read verify_chain Recompute chain_hash for a range of events and report any breaks. Returns verified count and broken entries.

FAQ

Questions about Audit event mcp

How do I prevent bulk modifications through Audit event mcp? +

The Audit event mcp server has 2 write tools including record_event, request_approval. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Audit event mcp.

How many tools does the Audit event MCP server expose? +

6 tools across 2 categories: Read, Write. 4 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on Audit event mcp? +

Register the Audit event MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Audit event mcp tool call.

Deterministic rules across all 6 Audit event mcp tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON AUDIT EVENT →

Instant setup, no code required.

6 Audit event mcp tools catalogued and risk-classified — across an index of 43,000+ MCP servers.