audit_list_logs

List recent audit log entries (most recent first).

Server LocalAnt yuga-hashimoto/localant
Category Read
Risk class Low
Parameters 00 required

What audit_list_logs does on LocalAnt

AI agents call audit_list_logs to retrieve information from LocalAnt without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why audit_list_logs needs a policy

This tool queries and retrieves audit log data without modifying, executing, or deleting anything. It is a straightforward read operation that poses minimal risk; the worst-case scenario is information disclosure of logs the requester likely has permission to access.

From the tool's definition Tool name contains 'list' and description explicitly states 'List recent audit log entries'; the verb 'list' is a read-only retrieval operation with no side effects.

Questions about audit_list_logs

What does the audit_list_logs tool do? +

List recent audit log entries (most recent first). It is categorised as a Read tool in the LocalAnt MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on audit_list_logs? +

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

What risk level is audit_list_logs? +

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

Can I rate-limit audit_list_logs? +

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

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

audit_list_logs is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.