create_sql_query_evidence

A execute tool on the ComplianceCow MCP server.

SERVERComplianceCow MCP Server SOURCEcompliancecow/cow-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about create_sql_query_evidence

What does the create_sql_query_evidence tool do? +

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.

How do I enforce a policy on create_sql_query_evidence? +

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.

What risk level is create_sql_query_evidence? +

create_sql_query_evidence is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit create_sql_query_evidence? +

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.

How do I block create_sql_query_evidence completely? +

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.

What MCP server provides create_sql_query_evidence? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of ComplianceCow MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.