create_sql_query_evidence
A execute tool on the ComplianceCow MCP server.
This record as markdown: /tools/compliancecow-cow-mcp/create-sql-query-evidence.md
What create_sql_query_evidence does on ComplianceCow MCP Server
AI agents invoke create_sql_query_evidence to trigger actions in ComplianceCow MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why create_sql_query_evidence is rated High
The tool name suggests it involves SQL query execution (Execute category) and evidence creation (Write category). Since Execute > Write in severity, and SQL execution can have significant side effects depending on the query, Execute is the most appropriate category. However, the empty description significantly lowers confidence.
From the tool's definition Tool name contains 'create' and 'sql_query' suggesting it executes SQL queries and/or creates evidence artifacts; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs create_sql_query_evidence safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ComplianceCow MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_sql_query_evidence, this is the rule to start with:
create_sql_query_evidence stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ComplianceCow MCP Server, apply this rule, and every create_sql_query_evidence call is checked against it from then on.
Questions about create_sql_query_evidence
create_sql_query_evidence is a execute tool on the ComplianceCow MCP Server MCP server. It is categorised as a Execute tool in the ComplianceCow MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ComplianceCow MCP Server MCP server in PolicyLayer and add a rule for create_sql_query_evidence: 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 ComplianceCow MCP Server. Nothing to install.
create_sql_query_evidence is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the create_sql_query_evidence 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 create_sql_query_evidence. 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.
create_sql_query_evidence is provided by the ComplianceCow MCP Server MCP server (compliancecow/cow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ComplianceCow MCP Server, and thousands of servers like it.
Across the catalogue