upload_evidence
A write tool on the ComplianceCow MCP server.
This record as markdown: /tools/compliancecow-cow-mcp/upload-evidence.md
What upload_evidence does on ComplianceCow MCP Server
AI agents use upload_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 upload_evidence is rated Medium
Despite empty description, the name strongly suggests writing/uploading evidence records to a compliance platform. This is reversible (Write, not Destructive) but could impact audit trails or compliance status if misused. Severity is medium because misuse could corrupt compliance records or create false evidence, but the impact is scoped to the compliance system rather than financial or critical infrastructure.
From the tool's definition Tool name 'upload_evidence' indicates creation/addition of evidence artifacts to the compliance system. Server description mentions 'auditable evidence' and 'automated remediation actions'.
Attacks that exploit this kind of access
The rule that runs upload_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 upload_evidence, this is the rule to start with:
upload_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 upload_evidence call is checked against it from then on.
Questions about upload_evidence
upload_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 upload_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.
upload_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 upload_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 upload_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.
upload_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