list_audit_logs
List recent audit log entries for this company. Filter by action, resource, resourceId, user, source, outcome, destructive flag, and created date range.
This record as markdown: /tools/io-favcrm-favcrm/list-audit-logs.md
What list_audit_logs does on FavCRM
AI agents call list_audit_logs to retrieve information from FavCRM 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 |
|---|---|---|---|
limit | integer | — | Maximum rows to return |
action | string | — | Exact tool/action name, e.g. delete_campaign |
source | string | — | Audit source, e.g. mcp, ai_agent, payment_webhook, merchant_api |
userId | string | — | Actor user ID |
outcome | string | — | Execution outcome |
resource | string | — | Resource name, e.g. campaigns |
resourceId | string | — | Resource ID |
destructive | boolean | — | Whether the audited tool was destructive |
createdAfter | string | — | ISO timestamp lower bound |
createdBefore | string | — | ISO timestamp upper bound |
Parameters from the server's own tool schema.
Why list_audit_logs is rated Low
This tool retrieves and queries existing audit log data without any side effects. It performs a read-only operation to view historical records. The 'destructive flag' mentioned is merely a filter parameter used to query logs, not an action the tool performs.
From the tool's definition Tool name 'list_audit_logs' and description 'List recent audit log entries' indicate a retrieval operation.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs list_audit_logs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FavCRM, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_audit_logs, this is the rule to start with:
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 FavCRM, apply this rule, and every list_audit_logs call is checked against it from then on.
Questions about list_audit_logs
List recent audit log entries for this company. Filter by action, resource, resourceId, user, source, outcome, destructive flag, and created date range. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.
list_audit_logs accepts 10 parameters: limit, action, source, userId, outcome, resource, resourceId, destructive, createdAfter, createdBefore. The full parameter table on this page comes from the server's own tool schema.
Register the FavCRM MCP server in PolicyLayer and add a rule for 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 FavCRM. Nothing to install.
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 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 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.
list_audit_logs is provided by the FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FavCRM, and thousands of servers like it.
This server
Across the catalogue