AI agents call export_contact_history_csv 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.
Based on the tool name, this tool exports contact interaction history as a CSV file. This is a read/export operation similar to the sibling tools 'export_contacts_csv', 'export_full_crm_csv', and 'export_todos_csv', which are all read operations. No data modification is implied. Confidence is reduced due to empty description.
From the tool's definition Tool name 'export_contact_history_csv' implies reading/exporting contact history data to CSV format; description is empty.
Documented attack patterns abuse exactly the kind of access export_contact_history_csv 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 export_contact_history_csv:
{
"version": "1",
"default": "deny",
"tools": {
"export_contact_history_csv": {}
}
}export_contact_history_csv 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.
export_contact_history_csv. 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 export_contact_history_csv: 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.
export_contact_history_csv 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 export_contact_history_csv 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 export_contact_history_csv. 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.
export_contact_history_csv 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.