update_metric_sql_query_evidence

A write tool on the ComplianceCow MCP server.

SERVERComplianceCow MCP Server SOURCEcompliancecow/cow-mcp

Medium RISK CLASS

Category Write

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/update-metric-sql-query-evidence.md

WHAT IT DOES

What update_metric_sql_query_evidence does on ComplianceCow MCP Server

AI agents use update_metric_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.

RISK

Why update_metric_sql_query_evidence is rated Medium

The name suggests updating a SQL query or evidence associated with a metric. 'Update' implies a reversible write operation modifying existing data. However, the description is empty so confidence is low. Given sibling tools are mostly write/configuration operations (add_metric, add_check_to_asset, attach_citation, etc.), a Write classification is most consistent.

From the tool's definition Tool name: update_metric_sql_query_evidence — description is empty or uninformative

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_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 update_metric_sql_query_evidence, this is the rule to start with:

update_metric_sql_query_evidence Rate-limited

update_metric_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_metric_sql_query_evidence": {
      "limits": [
        {
          "counter": "update_metric_sql_query_evidence_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ComplianceCow MCP Server, apply this rule, and every update_metric_sql_query_evidence call is checked against it from then on.

FAQ

Questions about update_metric_sql_query_evidence

What does the update_metric_sql_query_evidence tool do? +

update_metric_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.

How do I enforce a policy on update_metric_sql_query_evidence? +

Register the ComplianceCow MCP Server MCP server in PolicyLayer and add a rule for update_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.

What risk level is update_metric_sql_query_evidence? +

update_metric_sql_query_evidence is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_metric_sql_query_evidence? +

Yes. Add a rate_limit block to the update_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.

How do I block update_metric_sql_query_evidence completely? +

Set action: deny in the PolicyLayer policy for update_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.

What MCP server provides update_metric_sql_query_evidence? +

update_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.

KEEP EXPLORING

More on ComplianceCow MCP Server, and thousands of servers like it.

This server

All 209 ComplianceCow MCP Server tools →

Across the catalogue

generate_evidence_manifest on Android Forensics ADB MCP Server →aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →