fetch_assessment_run_leaf_control_evidence
A read tool on the ComplianceCow MCP server.
This record as markdown: /tools/compliancecow-cow-mcp/fetch-assessment-run-leaf-control-evidence.md
What fetch_assessment_run_leaf_control_evidence does on ComplianceCow MCP Server
AI agents call fetch_assessment_run_leaf_control_evidence to retrieve information from ComplianceCow MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why fetch_assessment_run_leaf_control_evidence is rated Low
This tool retrieves assessment run evidence related to leaf controls in a compliance system. 'Fetch' is a read operation that queries existing data without side effects. No deletion, modification, code execution, or financial impact is indicated. The sibling tools include write-oriented operations (add_*, assign_*, attach_*), but this tool's naming clearly indicates read-only functionality.
From the tool's definition Tool name 'fetch_assessment_run_leaf_control_evidence' contains 'fetch', which indicates data retrieval with no modification.
Attacks that exploit this kind of access
The rule that runs fetch_assessment_run_leaf_control_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 fetch_assessment_run_leaf_control_evidence, this is the rule to start with:
fetch_assessment_run_leaf_control_evidence is read-only, so it stays allowed. 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 fetch_assessment_run_leaf_control_evidence call is checked against it from then on.
Questions about fetch_assessment_run_leaf_control_evidence
fetch_assessment_run_leaf_control_evidence is a read tool on the ComplianceCow MCP Server MCP server. It is categorised as a Read tool in the ComplianceCow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ComplianceCow MCP Server MCP server in PolicyLayer and add a rule for fetch_assessment_run_leaf_control_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.
fetch_assessment_run_leaf_control_evidence is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the fetch_assessment_run_leaf_control_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 fetch_assessment_run_leaf_control_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.
fetch_assessment_run_leaf_control_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