Add a note to a company.
AI agents use crm_add_company_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 or modifies data (adding a note) in a reversible manner. The operation can be undone by deleting the note. No code execution, data destruction, or financial operations occur. The blast radius is limited to adding a single note attachment to a company record, which is typical CRM functionality with minimal risk.
From the tool's definition Tool name 'crm_add_company_note' and description 'Add a note to a company' indicate the tool creates new note data associated with a company entity.
Attacks that exploit this kind of access
Add a note to a company. 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_company_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_company_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_company_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_company_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_company_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 →