Guided Senzing SDK setup across 5 platforms (linux_apt, linux_yum, macos_arm, windows, docker) and 5 languages (Python, Java, C#, Rust, TypeScript). Returns real, compilable code snippets extracted from official GitHub repositories with source attribution. Use this INSTEAD of hand-coding install ...
Part of the Senzing server.
Free to start. No card required.
AI agents may call sdk_guide to permanently remove or destroy resources in Senzing. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call sdk_guide in a loop, permanently destroying resources in Senzing. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
{
"version": "1",
"default": "deny",
"hide": [
"sdk_guide"
]
}See the full Senzing policy for all 13 tools.
These attack patterns abuse exactly the kind of access sdk_guide gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Guided Senzing SDK setup across 5 platforms (linux_apt, linux_yum, macos_arm, windows, docker) and 5 languages (Python, Java, C#, Rust, TypeScript). Returns real, compilable code snippets extracted from official GitHub repositories with source attribution. Use this INSTEAD of hand-coding install commands or engine configuration — hand-coded setups commonly get paths wrong (CONFIGPATH, RESOURCEPATH, SUPPORTPATH), miss the SQLite schema creation step, skip EULA acceptance, and produce invalid SENZING_ENGINE_CONFIGURATION_JSON. Two use cases: (1) Quick test load — install Senzing locally, load mapped data into SQLite, and verify entity resolution results. No external database needed. (2) Build your own pipeline — get platform-specific install commands, SDK configuration code, record loading templates, and export patterns for production use. Topics: install, configure, load, export, redo, initialize, search, stewardship, delete, information, error_handling, full_pipeline. Export delegates to generate_scaffold. Returns decision trees when platform/language not specified.. It is categorised as a Destructive tool in the Senzing MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Senzing MCP server in PolicyLayer and add a rule for sdk_guide: 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 Senzing. Nothing to install.
sdk_guide 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 sdk_guide 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 sdk_guide. 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.
sdk_guide is provided by the Senzing MCP server (senzing/entity-resolution). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 Senzing tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.