Get all deals associated with a specific contact ID.
AI agents call crm_get_deals_by_contact to retrieve information from Medicus CRM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves deal data linked to a contact. It performs a read-only operation that does not create, modify, delete, or execute any actions. The verb 'Get' and the passive data retrieval purpose confirm this is a Read category tool. Severity is low because retrieving existing CRM data poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'crm_get_deals_by_contact' and description 'Get all deals associated with a specific contact ID' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get all deals associated with a specific contact ID. It is categorised as a Read tool in the Medicus CRM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Medicus CRM MCP Server MCP server in PolicyLayer and add a rule for crm_get_deals_by_contact: 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_get_deals_by_contact 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 crm_get_deals_by_contact 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_get_deals_by_contact. 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_get_deals_by_contact 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 →