dedupe_records
Find and remove duplicate records (CRM contacts, leads, customers, products) in a JSON array. Modes: exact, normalized (emails: case, Gmail dots and +tags; phones: punctuation and country prefix; URLs: scheme, www, tracking params; names: accents, honorifics, word order; companies: Inc / Ltd / Gm...
This record as markdown: /tools/com-it-scorptech-x402/dedupe-records.md
What dedupe_records does on ScorpTech x402 API
AI agents call dedupe_records to permanently remove resources in ScorpTech x402 API, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
keep | string | — | |
mode | string | — | |
merge | boolean | — | Fill empty fields of the kept record from its duplicates |
types | object | — | Optional field → type map (email, phone, url, name, company, text, number, exact); auto-detected from field names and values otherwise |
fields | array | — | Fields to compare (default: every field) |
records | array | Yes | Array of record objects (max 5000) |
threshold | number | — | Fuzzy mode: minimum weighted similarity |
includeRecords | boolean | — | Return the de-duplicated records |
Parameters from the server's own tool schema.
Why dedupe_records is rated Critical
An AI agent that decides to call dedupe_records doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from ScorpTech x402 API is gone. There is no undo for destructive operations.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs dedupe_records safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dedupe_records, this is the rule to start with:
dedupe_records is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect ScorpTech x402 API, apply this rule, and every dedupe_records call is checked against it from then on.
Questions about dedupe_records
Find and remove duplicate records (CRM contacts, leads, customers, products) in a JSON array. Modes: exact, normalized (emails: case, Gmail dots and +tags; phones: punctuation and country prefix; URLs: scheme, www, tracking params; names: accents, honorifics, word order; companies: Inc / Ltd / GmbH suffixes) and fuzzy (Jaro-Winkler / token similarity with weighted fields, blocking + sorted neighbourhood so 5,000 records stay fast). Groups transitive matches, keeps the first / last / most complete record, optionally merges missing fields from the duplicates, and returns the unique records plus every duplicate group with its score. Price: $0.003 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/dedupe-records. It is categorised as a Destructive tool in the ScorpTech x402 API MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
dedupe_records accepts 8 parameters: keep, mode, merge, types, fields, records, threshold, includeRecords. Required: records. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for dedupe_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 ScorpTech x402 API. Nothing to install.
dedupe_records is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the dedupe_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 dedupe_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.
dedupe_records is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
Across the catalogue