AI agents call get_contact_history to retrieve information from 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 retrieves or queries historical data about a contact's interactions without modifying or deleting anything. It falls into Read category. Severity is medium because access to CRM contact history could expose sensitive personal or business information if misused by an AI agent (e.g., to extract data about competitors' interactions or confidential client details), but it does not create, destroy, or move…
From the tool's definition Tool name 'get_contact_history' indicates retrieval of historical interaction data for contacts. Description is empty, but sibling tools include 'export_contact_history_csv' and the server manages 'interaction history', confirming this retrieves contact…
Documented attack patterns abuse exactly the kind of access get_contact_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CRM MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_contact_history:
{
"version": "1",
"default": "deny",
"tools": {
"get_contact_history": {}
}
}get_contact_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_contact_history. It is categorised as a Read tool in the CRM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CRM MCP Server MCP server in PolicyLayer and add a rule for get_contact_history: 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 CRM MCP Server. Nothing to install.
get_contact_history 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 get_contact_history 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 get_contact_history. 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.
get_contact_history is provided by the CRM MCP Server MCP server (nxt3d/mcp-crm). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CRM MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 CRM MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.