list_notes
List notes attached to a member/account, booking, or ticket.
This record as markdown: /tools/io-favcrm-favcrm/list-notes.md
What list_notes does on FavCRM
AI agents call list_notes 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 10) |
entityId | string | Yes | The entity ID |
entityType | string | Yes | Type of entity the notes are on |
Parameters from the server's own tool schema.
Why list_notes is rated Low
This tool retrieves or queries existing notes without side effects. It performs a read-only operation consistent with the 'Read' category (search, list, get, fetch). The verb 'list' explicitly indicates data retrieval. There is no capability to create, modify, delete, execute code, or commit financial actions. Low severity due to limited blast radius—misuse would only expose existing note data.
From the tool's definition Tool name 'list_notes' and description 'List notes attached to a member/account, booking, or ticket' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
The rule that runs list_notes 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_notes, this is the rule to start with:
list_notes 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_notes call is checked against it from then on.
Questions about list_notes
List notes attached to a member/account, booking, or ticket. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.
list_notes accepts 3 parameters: limit, entityId, entityType. Required: entityId, entityType. 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_notes: 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_notes 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_notes 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_notes. 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_notes 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