get_audit_log
Returns recent LMCP tool call history from the local audit log. Each entry shows timestamp, tool name, call source (local/cloud), success status, and duration. Useful for GDPR Article 30 compliance reporting and debugging.
This record as markdown: /tools/com-local-mcp-local-mcp/get-audit-log.md
What get_audit_log does on Local
AI agents call get_audit_log to retrieve information from Local 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 |
|---|---|---|---|
ok | boolean | — | Filter to successes (true) or failures (false) only (optional) |
tool | string | — | Filter to entries for a specific tool name (optional) |
limit | integer | — | Number of recent entries to return (default 50, max 200) |
Parameters from the server's own tool schema.
Why get_audit_log is rated Low
This tool reads and queries audit log data for compliance and debugging purposes. It has no capability to modify, delete, or execute operations—it only retrieves existing log entries.
From the tool's definition Tool description states it 'Returns recent LMCP tool call history' and retrieves entries from 'the local audit log' with 'timestamp, tool name, call source, success status, and duration.' The verb 'Returns' and action of querying historical logs indicates…
Attacks that exploit this kind of access
The rule that runs get_audit_log safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_audit_log, this is the rule to start with:
get_audit_log is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every get_audit_log call is checked against it from then on.
Questions about get_audit_log
Returns recent LMCP tool call history from the local audit log. Each entry shows timestamp, tool name, call source (local/cloud), success status, and duration. Useful for GDPR Article 30 compliance reporting and debugging. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
get_audit_log accepts 3 parameters: ok, tool, limit. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for get_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 Local. Nothing to install.
get_audit_log is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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.
Set action: deny in the PolicyLayer policy for get_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.
get_audit_log is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue