Protective check on SQL queries — catches injection or destructive operations before execution, so a malformed or injected query doesn't damage data on your watch. Call this BEFORE executing any SQL query generated by an LLM or constructed from user input. DECISION LOGIC: - If blocked=true: do NO...
Risk signalsAccepts freeform code/query input (query)
Part of the Shrike Security server.
Free to start. No card required.
AI agents call scan_sql_query to retrieve information from Shrike Security without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though scan_sql_query only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"scan_sql_query": {}
}
}See the full Shrike Security policy for all 12 tools.
These attack patterns abuse exactly the kind of access scan_sql_query gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Protective check on SQL queries — catches injection or destructive operations before execution, so a malformed or injected query doesn't damage data on your watch. Call this BEFORE executing any SQL query generated by an LLM or constructed from user input. DECISION LOGIC: - If blocked=true: do NOT execute the query. Return the user_message and log audit.scan_id for security review. - If blocked=false: the query is safe to execute. Checks for: - SQL injection patterns (UNION, stacked queries, tautologies, blind injection) - Destructive operations (DROP, TRUNCATE, DELETE without WHERE) - Privilege escalation (GRANT, CREATE USER) - PII extraction (queries targeting password/SSN/credit card columns) Read-only queries (SELECT) are scanned for injection and PII extraction. Write queries (INSERT, UPDATE, DELETE, DROP) receive additional destructive operation analysis. All queries should be scanned regardless of type — injection attacks frequently use SELECT as a vector. Set allowDestructive=true to permit DROP/TRUNCATE for migrations. Pass database name for context-aware analysis. Enterprise context: Critical for any agent with database access. Prevents both malicious and accidental data destruction or unauthorized data extraction. ERROR HANDLING: If this tool returns an error or is unavailable, default to BLOCKING the query. Do NOT execute unscanned SQL.. It is categorised as a Read tool in the Shrike Security MCP Server, which means it retrieves data without modifying state.
Register the Shrike Security MCP server in PolicyLayer and add a rule for scan_sql_query: 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 Shrike Security. Nothing to install.
scan_sql_query 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 scan_sql_query 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 scan_sql_query. 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.
scan_sql_query is provided by the Shrike Security MCP server (shrike-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 12 Shrike Security 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.