create_metric_sql_query_evidence
A other tool on the ComplianceCow MCP server.
This record as markdown: /tools/compliancecow-cow-mcp/create-metric-sql-query-evidence.md
What create_metric_sql_query_evidence does on ComplianceCow MCP Server
AI agents call create_metric_sql_query_evidence as a supporting operation in ComplianceCow MCP Server workflows.
Why create_metric_sql_query_evidence is rated Low
The description is empty, so classification relies solely on the tool name. The name contains 'create' (suggesting Write), 'sql_query' (suggesting Execute), and 'evidence' (suggesting data retrieval or compliance artifact generation). Given the ambiguity across multiple categories, and following the severity precedence rule, Execute is plausible but confidence is low due to lack of description.
From the tool's definition Tool description is empty and uninformative; name suggests 'create_metric_sql_query_evidence' which could involve writing/executing SQL queries
Attacks that exploit this kind of access
The rule that runs create_metric_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_metric_sql_query_evidence, this is the rule to start with:
create_metric_sql_query_evidence gets a rate cap, and 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_metric_sql_query_evidence call is checked against it from then on.
Questions about create_metric_sql_query_evidence
create_metric_sql_query_evidence is a other tool on the ComplianceCow MCP Server MCP server. It is categorised as a Other tool in the ComplianceCow MCP Server MCP Server, which means it performs auxiliary operations.
Register the ComplianceCow MCP Server MCP server in PolicyLayer and add a rule for create_metric_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_metric_sql_query_evidence is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the create_metric_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_metric_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_metric_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