get_audit_log
Fetch a single audit log entry by ID, including before/after snapshots when available.
This record as markdown: /tools/io-favcrm-favcrm/get-audit-log.md
What get_audit_log does on FavCRM
AI agents call get_audit_log 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 |
|---|---|---|---|
auditLogId | string | Yes | Audit log ID |
Parameters from the server's own tool schema.
Why get_audit_log is rated Low
This tool retrieves historical audit log data without modifying, deleting, or executing any operations. It is a straightforward read operation that queries existing audit records. The low severity reflects that audit logs are typically non-sensitive business records, and fetching them carries minimal risk even if misused by an AI agent.
From the tool's definition Tool name is 'get_audit_log' and description states 'Fetch a single audit log entry by ID, including before/after snapshots when available.' The verb 'Fetch' and the retrieval-only nature indicate no data modification or execution occurs.
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 FavCRM, 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 FavCRM, apply this rule, and every get_audit_log call is checked against it from then on.
Questions about get_audit_log
Fetch a single audit log entry by ID, including before/after snapshots when available. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.
get_audit_log accepts 1 parameter: auditLogId. Required: auditLogId. 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 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 FavCRM. 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 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