Attach a note to contact/company/deal/lead.
AI agents use crm_add_note to create or update resources in Medicus CRM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Medicus CRM MCP Server environment.
This tool creates new data (notes) within a CRM system but does so reversibly—notes can be edited or deleted. It modifies entity records by adding information but does not irreversibly destroy data, execute arbitrary code, trigger financial transactions, or perform system commands. The blast radius is limited to note creation on existing CRM records.
From the tool's definition Tool name 'crm_add_note' and description 'Attach a note to contact/company/deal/lead' indicates creating and appending new note records to existing CRM entities.
Attacks that exploit this kind of access
Attach a note to contact/company/deal/lead. It is categorised as a Write tool in the Medicus CRM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Medicus CRM MCP Server MCP server in PolicyLayer and add a rule for crm_add_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 Medicus CRM MCP Server. Nothing to install.
crm_add_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 crm_add_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 crm_add_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.
crm_add_note is provided by the Medicus CRM MCP Server MCP server (soundrolling/crmmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →