Incomplete referenced artifact analysis
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md | [Syntax Rules](rules/syntax_rules.yaml) | 34 syntax check rule definitions |
Security audit
Security checks for vulnerabilities and agentic risk
This skill checks SQL locally without database access, but its validation can incorrectly report incomplete statements as passing.
Use this as an offline advisory linter, not as authorization to execute SQL: a passing report does not establish valid or safe SQL. Reports reproduce the submitted SQL. Cluster credentials are unnecessary; any separately requested live profiling should have explicit authorization and database-side limits. Independent inspection addressed the scanner's material coverage gaps, but comprehensive grammar correctness was not established.
Referenced artifact was not completely inspected
| [Syntax Rules](rules/syntax_rules.yaml) | 34 syntax check rule definitions |
Referenced artifact was not completely inspected
| [Specification Rules](rules/spec_rules.yaml) | 40 specification check rule definitions |
Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.
)
def _parse_delete(self):
"""Parse DELETE statement"""
self._expect_keyword("DELETE")
self._expect_keyword("FROM")
table = self._consume_qualified_name()
PERF005 requests execution-based profiling through MCP and applies it to SELECT, UPDATE, and DELETE without specifying authorization, isolation, or resource limits. Unlike offline syntax checking, execution-based analysis can consume production resources and, depending on database support and execution semantics, risk modifying data; the supplied configuration does not establish that such execution actually occurs.
The generic fallback consumes tokens without validating statement grammar or recording an unsupported-validation error, while is_valid() treats the absence of errors as success. Consequently, recognized statement types without dedicated parsers can receive a misleading valid result, undermining the advertised SQL review and potentially bypassing downstream checks that trust this result; this code does not itself execute SQL.