13 tools from the Senzing MCP Server, categorised by risk level.
View the Senzing policy →analyze_record Get the Senzing JSON analyzer script with commands to validate and analyze mapped data files client-side. The analyzer validates records against th... download_resource Download workflow resources. Returns URLs — download and save to disk. Supports batch: pass `filenames` (array) to retrieve multiple resources in o... explain_error_code Explain a Senzing error code with causes and resolution steps. Accepts formats: SENZ0005, SENZ-0005, 0005, or just 5. Returns error class, common c... find_examples Find working SOURCE CODE examples from 27 indexed Senzing GitHub repositories. Indexes only source code files (.py, .java, .cs, .rs) and READMEs — ... 2/5 get_capabilities Get server version, capabilities overview, available tools, suggested workflows, and getting started guidance. Returns server_info with name, versi... get_sample_data Get real sample data from CORD (Collections Of Relatable Data) datasets. Use dataset='list' to discover available datasets, source='list' to see ve... get_sdk_reference Get authoritative Senzing SDK reference data for flags, migration, and API details. Use this instead of search_docs when you need precise SDK metho... 2/5 search_docs Full-text BM25 search across all indexed Senzing documentation (~2175 chunks). Returns ranked results with excerpts. Use 'category' to filter: sdk,... 2/5 generate_scaffold Generate SDK scaffold code for common workflows. Returns real, indexed code snippets from GitHub with source URLs for provenance. Use this INSTEAD ... 2/5 submit_feedback Submit feedback about the Senzing MCP server. IMPORTANT: Before calling this tool, you MUST show the user the exact message you plan to send and ge... 2/5 mapping_workflow Map source data to Senzing entity resolution format through a guided 8-step workflow. Core steps 1-4: profile source data, plan entity structure, m... 5/5 sdk_guide Guided Senzing SDK setup across 5 platforms (linux_apt, linux_yum, macos_arm, windows, docker) and 5 languages (Python, Java, C#, Rust, TypeScript)... 4/5 The Senzing MCP server exposes 13 tools across 4 categories: Read, Write, Destructive, Execute.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Senzing server.
Senzing tools are categorised as Read (8), Write (2), Destructive (2), Execute (1). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept