create_note
Add a note to a member/account, booking, ticket, or invoice.
This record as markdown: /tools/io-favcrm-favcrm/create-note.md
What create_note does on FavCRM
AI agents use create_note to create or update resources in FavCRM, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FavCRM environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | string | Yes | Note content |
entityId | string | Yes | The entity ID |
isPinned | boolean | — | Pin this note to the top |
entityType | string | Yes | Type of entity |
Parameters from the server's own tool schema.
Why create_note is rated Medium
This tool creates or appends notes to existing entities within the CRM system. Notes are typically non-destructive, reversible additions of metadata or commentary. The action is Write-category because it modifies records (adding data), but severity is low because notes do not affect core business logic, financial operations, or have wide blast radius — a misused note might clutter records but causes minimal business…
From the tool's definition Tool description states 'Add a note to a member/account, booking, ticket, or invoice' — the verb 'Add' indicates creation of new data.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs create_note 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 create_note, this is the rule to start with:
create_note stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 create_note call is checked against it from then on.
Questions about create_note
Add a note to a member/account, booking, ticket, or invoice. It is categorised as a Write tool in the FavCRM MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_note accepts 4 parameters: body, entityId, isPinned, entityType. Required: body, 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 create_note: 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.
create_note is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_note 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 create_note. 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.
create_note 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