fetch_execution_progress
A read tool on the ComplianceCow MCP server.
This record as markdown: /tools/compliancecow-cow-mcp/fetch-execution-progress.md
What fetch_execution_progress does on ComplianceCow MCP Server
AI agents call fetch_execution_progress 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_execution_progress is rated Low
The 'fetch' verb indicates data retrieval with no side effects. Even in the context of a compliance platform with remediation capabilities, fetching progress is a read-only operation that queries state rather than modifies it. The empty description reduces confidence slightly, but the verb choice is strongly indicative of Read category.
From the tool's definition Tool name 'fetch_execution_progress' uses the verb 'fetch', which retrieves data without modification. The empty description limits certainty, but the naming pattern is consistent with read-only operations that query the status or progress of existing…
Attacks that exploit this kind of access
The rule that runs fetch_execution_progress 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_execution_progress, this is the rule to start with:
fetch_execution_progress 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_execution_progress call is checked against it from then on.
Questions about fetch_execution_progress
fetch_execution_progress 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_execution_progress: 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_execution_progress 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_execution_progress 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_execution_progress. 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_execution_progress 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