crm_export_import_csv
Build a HubSpot-import CSV (base64-encoded) from prospects. When dedup_against_hubspot (default true), drops prospects whose email already exists in HubSpot (concurrency <=5). Columns: Email, First Name, Last Name, Job Title, Company, Company Domain, Country, Industry, Number of Employees [, HubS...
This record as markdown: /tools/digital-crew-technologies-max-mcp-server/crm-export-import-csv.md
What crm_export_import_csv does on Max MCP Server
AI agents use crm_export_import_csv to create or update resources in Max MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Max MCP Server environment.
Why crm_export_import_csv is rated Medium
This tool creates a formatted CSV file (base64-encoded) intended for HubSpot import, which is a reversible data modification operation. While it includes a read-like deduplication step, its primary purpose is to generate and prepare data for writing into HubSpot. This qualifies as Write rather than Read.
From the tool's definition Tool description states it 'Build[s] a HubSpot-import CSV' and is designed to prepare data for import into HubSpot CRM. The return value includes csv_base64, row_count, deduped_count, indicating it creates/transforms data for writing to an external system.
Attacks that exploit this kind of access
The rule that runs crm_export_import_csv safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Max MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crm_export_import_csv, this is the rule to start with:
crm_export_import_csv stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Max MCP Server, apply this rule, and every crm_export_import_csv call is checked against it from then on.
Questions about crm_export_import_csv
Build a HubSpot-import CSV (base64-encoded) from prospects. When dedup_against_hubspot (default true), drops prospects whose email already exists in HubSpot (concurrency <=5). Columns: Email, First Name, Last Name, Job Title, Company, Company Domain, Country, Industry, Number of Employees [, HubSpot Owner ID when include_assignment]. Returns { csv_base64, row_count, deduped_count, deduped:[{ email, existing_id }] }. It is categorised as a Write tool in the Max MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Max MCP Server MCP server in PolicyLayer and add a rule for crm_export_import_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 Max MCP Server. Nothing to install.
crm_export_import_csv 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_export_import_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 crm_export_import_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.
crm_export_import_csv is provided by the Max MCP Server MCP server (digital-crew-technologies/max-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Max MCP Server, and thousands of servers like it.
This server
Across the catalogue