update_sql_query_evidence
A write tool on the ComplianceCow MCP server.
This record as markdown: /tools/compliancecow-cow-mcp/update-sql-query-evidence.md
What update_sql_query_evidence does on ComplianceCow MCP Server
AI agents use update_sql_query_evidence to create or update resources in ComplianceCow MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ComplianceCow MCP Server environment.
Why update_sql_query_evidence is rated Medium
The tool performs a Write operation—it updates SQL query evidence, modifying compliance/audit records reversibly. While the empty description prevents absolute certainty, the context of a compliance platform combined with 'update_' semantics and sibling tools like 'attach_citation_to_control_config' and 'attach_rule_to_control' (which also modify compliance artifacts) indicates this creates or modifies evidence…
From the tool's definition Tool name 'update_sql_query_evidence' indicates modification of evidence data. The 'update_' prefix confirms reversible write operation.
Attacks that exploit this kind of access
The rule that runs update_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 update_sql_query_evidence, this is the rule to start with:
update_sql_query_evidence stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 update_sql_query_evidence call is checked against it from then on.
Questions about update_sql_query_evidence
update_sql_query_evidence is a write tool on the ComplianceCow MCP Server MCP server. It is categorised as a Write tool in the ComplianceCow MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ComplianceCow MCP Server MCP server in PolicyLayer and add a rule for update_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.
update_sql_query_evidence is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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 update_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.
update_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.
This server
Across the catalogue