Critical-risk tools in Senzing
2 of the 13 tools in Senzing are classified as critical risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at critical risk
-
mapping_workflowDestructive 5/5Map source data to Senzing entity resolution format through a guided 8-step workflow. Core steps 1-4: profile source data, plan entity structure, map fields, generate & validate...
-
sdk_guideDestructive 4/5Guided 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 cod...
Attacks that target this class
Critical-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.
More on Senzing
Enforce policy on Senzing
One command generates a policy scaffold for every server in your MCP config.
npx -y @policylayer/intercept init