neuron_list_audit_logs
Retrieve audit logs for the organization, showing a chronological record of actions performed by members. Supports filtering by action type and resource.
This record as markdown: /tools/io-github-conquext-neuron/neuron-list-audit-logs.md
What neuron_list_audit_logs does on Neuron
AI agents call neuron_list_audit_logs to retrieve information from Neuron 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 |
|---|---|---|---|
page | integer | — | Page number for pagination (default: 1) |
limit | integer | — | Number of log entries per page (default: 20) |
action | string | — | Filter by action type (e.g., 'CREATE', 'UPDATE', 'DELETE') |
resourceType | string | — | Filter by resource type (e.g., 'USER', 'ORGANIZATION', 'BOT', 'CAMPAIGN') |
Parameters from the server's own tool schema.
Why neuron_list_audit_logs is rated Low
This tool retrieves and filters existing audit log data without side effects. It is a standard auditing/logging read operation with minimal security risk, appropriate for compliance and transparency purposes. The blast radius of misuse (e.g., an agent reading audit logs) is low compared to write, execute, or destructive operations.
From the tool's definition Tool name and description indicate 'Retrieve audit logs' — a read-only operation that queries historical records. No modification, execution, deletion, or financial operations are described.
Attacks that exploit this kind of access
The rule that runs neuron_list_audit_logs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Neuron, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For neuron_list_audit_logs, this is the rule to start with:
neuron_list_audit_logs 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 Neuron, apply this rule, and every neuron_list_audit_logs call is checked against it from then on.
Questions about neuron_list_audit_logs
Retrieve audit logs for the organization, showing a chronological record of actions performed by members. Supports filtering by action type and resource. It is categorised as a Read tool in the Neuron MCP Server, which means it retrieves data without modifying state.
neuron_list_audit_logs accepts 4 parameters: page, limit, action, resourceType. The full parameter table on this page comes from the server's own tool schema.
Register the Neuron MCP server in PolicyLayer and add a rule for neuron_list_audit_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 Neuron. Nothing to install.
neuron_list_audit_logs 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 neuron_list_audit_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.
Set action: deny in the PolicyLayer policy for neuron_list_audit_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.
neuron_list_audit_logs is provided by the Neuron MCP server (neuron-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Neuron, and thousands of servers like it.
This server
Across the catalogue