search_audit_logs
Search audit logs by free text across action, resource, resource ID, changes JSON, and metadata JSON.
This record as markdown: /tools/io-favcrm-favcrm/search-audit-logs.md
What search_audit_logs does on FavCRM
AI agents call search_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 |
query | string | Yes | Text to search for |
createdAfter | string | — | ISO timestamp lower bound |
createdBefore | string | — | ISO timestamp upper bound |
Parameters from the server's own tool schema.
Why search_audit_logs is rated Low
Searching audit logs is a retrieval operation with no side effects. It queries existing data to surface information about past actions, resource changes, and metadata. This is a pure Read operation.
From the tool's definition Tool name explicitly says 'search' and description states it 'Search[es] audit logs by free text' — a read-only query operation. No modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
The rule that runs search_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 search_audit_logs, this is the rule to start with:
search_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 search_audit_logs call is checked against it from then on.
Questions about search_audit_logs
Search audit logs by free text across action, resource, resource ID, changes JSON, and metadata JSON. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.
search_audit_logs accepts 4 parameters: limit, query, createdAfter, createdBefore. Required: query. 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 search_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.
search_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 search_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 search_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.
search_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