check_form_progress

A read tool on the ComplianceCow MCP server.

SERVERComplianceCow MCP Server SOURCEcompliancecow/cow-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/compliancecow-cow-mcp/check-form-progress.md

WHAT IT DOES

What check_form_progress does on ComplianceCow MCP Server

AI agents call check_form_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.

RISK

Why check_form_progress is rated Low

The tool name strongly implies a query or status check operation that retrieves progress information about a form. This is a read-only operation with no data modification, deletion, or external execution. The sibling tools include many write/modify operations (add_*, attach_*, assign_), but this one appears to be a passive inspection tool.

From the tool's definition Tool name 'check_form_progress' suggests querying or retrieving the status/state of a form. The empty description limits certainty, but the naming convention and context (compliance/audit platform retrieving dashboards and insights) indicates data retrieval…

Attacks that exploit this kind of access

RECOMMENDED RULE

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

check_form_progress Allowed

check_form_progress is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_form_progress": {}
  }
}

ALLOW ONLY 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 check_form_progress call is checked against it from then on.

FAQ

Questions about check_form_progress

What does the check_form_progress tool do? +

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

How do I enforce a policy on check_form_progress? +

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

What risk level is check_form_progress? +

check_form_progress is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_form_progress? +

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

How do I block check_form_progress completely? +

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

What MCP server provides check_form_progress? +

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

KEEP EXPLORING

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

This server

All 209 ComplianceCow MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →