list_duplicate_records
List pending duplicate pairs for prospects (default) or organizations, each with match_type, confidence and a summary of both records. Returns {data: Pair[], counts} (pending counts per match type). Merging is a human action in the app.
This record as markdown: /tools/digital-crew-technologies-max-mcp-server/list-duplicate-records.md
What list_duplicate_records does on Max MCP Server
AI agents call list_duplicate_records to retrieve information from Max MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_duplicate_records is rated Low
Tool retrieves duplicate record data without modifying or deleting anything; read-only query operation.
From the tool's definition List pending duplicate pairs for prospects or organizations with match_type and confidence
Attacks that exploit this kind of access
The rule that runs list_duplicate_records 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 list_duplicate_records, this is the rule to start with:
list_duplicate_records is read-only, so it stays allowed. 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 list_duplicate_records call is checked against it from then on.
Questions about list_duplicate_records
List pending duplicate pairs for prospects (default) or organizations, each with match_type, confidence and a summary of both records. Returns {data: Pair[], counts} (pending counts per match type). Merging is a human action in the app. It is categorised as a Read tool in the Max MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Max MCP Server MCP server in PolicyLayer and add a rule for list_duplicate_records: 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.
list_duplicate_records 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 list_duplicate_records 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 list_duplicate_records. 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.
list_duplicate_records 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