list_notification_logs
List notification delivery logs for the current company. Recipients are masked by default for incident-response safety.
This record as markdown: /tools/io-favcrm-favcrm/list-notification-logs.md
What list_notification_logs does on FavCRM
AI agents call list_notification_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 | number | — | Max results (default 50, max 100) |
dateTo | string | — | ISO timestamp upper bound |
status | string | — | Status filter |
channel | string | — | Notification channel filter |
dateFrom | string | — | ISO timestamp lower bound |
entityId | string | — | Entity ID filter |
eventType | string | — | Event type filter |
recipient | string | — | Substring search on recipient |
Parameters from the server's own tool schema.
Why list_notification_logs is rated Low
This tool retrieves historical notification delivery data. The description confirms read-only intent ('List notification delivery logs'), and the masking of recipient information suggests security awareness. No creation, modification, deletion, code execution, or financial transactions occur.
From the tool's definition Tool name contains 'list' and description states it 'List[s] notification delivery logs' — this is purely a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_notification_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_notification_logs, this is the rule to start with:
list_notification_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_notification_logs call is checked against it from then on.
Questions about list_notification_logs
List notification delivery logs for the current company. Recipients are masked by default for incident-response safety. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.
list_notification_logs accepts 8 parameters: limit, dateTo, status, channel, dateFrom, entityId, eventType, recipient. 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_notification_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_notification_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_notification_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_notification_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_notification_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