Associate a contact with a deal (creates row in deal_contacts).
AI agents use crm_link_contact_deal 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 a new association record linking a contact to a deal in the CRM database. It is reversible (the association can be deleted via a separate tool like crm_cancel_deal or an update operation), making it a Write action rather than Destructive.
From the tool's definition Tool description states 'Associate a contact with a deal (creates row in deal_contacts)' — the word 'creates' indicates a new data row is being added to the database.
Attacks that exploit this kind of access
Associate a contact with a deal (creates row in deal_contacts). 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_link_contact_deal: 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_link_contact_deal 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_link_contact_deal 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_link_contact_deal. 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_link_contact_deal 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 →