unified_sink_detect
Detect dangerous sink patterns (SQL injection, XSS, etc.) across Python, JS, TS, and Java.
This record as markdown: /tools/3d-tech-solutions-code-scalpel/unified-sink-detect.md
What unified_sink_detect does on Code Scalpel
AI agents call unified_sink_detect to retrieve information from Code Scalpel without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why unified_sink_detect is rated Low
This tool performs static analysis to identify vulnerable code patterns (SQL injection, XSS sinks). It retrieves and examines code to report findings, with no capability to execute, modify, delete, or move money. The analysis itself has no side effects on systems or data—it only reads and reports. Severity is low because misuse would result in false alerts or missed detections, not unauthorized access or damage.
From the tool's definition Tool name 'unified_sink_detect' and description 'Detect dangerous sink patterns' indicates analysis and detection of security issues, not execution or modification of code.
Attacks that exploit this kind of access
The rule that runs unified_sink_detect safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Code Scalpel, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For unified_sink_detect, this is the rule to start with:
unified_sink_detect 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 Code Scalpel, apply this rule, and every unified_sink_detect call is checked against it from then on.
Questions about unified_sink_detect
Detect dangerous sink patterns (SQL injection, XSS, etc.) across Python, JS, TS, and Java. It is categorised as a Read tool in the Code Scalpel MCP Server, which means it retrieves data without modifying state.
Register the Code Scalpel MCP server in PolicyLayer and add a rule for unified_sink_detect: 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 Code Scalpel. Nothing to install.
unified_sink_detect 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 unified_sink_detect 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 unified_sink_detect. 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.
unified_sink_detect is provided by the Code Scalpel MCP server (3d-tech-solutions/code-scalpel). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Code Scalpel, and thousands of servers like it.
This server
Across the catalogue