workflow.progress
Return compact recomputed progress without changing evidence or acceptance state.
This record as markdown: /tools/visionmcp/workflow.progress.md
What workflow.progress does on Visionmcp
AI agents call workflow.progress to retrieve information from Visionmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why workflow.progress is rated Low
This tool retrieves and returns progress information as a query operation with no side effects. The explicit statement that it does not change evidence or acceptance state confirms it is a read-only operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool description states it will 'Return compact recomputed progress without changing evidence or acceptance state' — explicitly indicating no modifications, only retrieval of computed state information.
Attacks that exploit this kind of access
The rule that runs workflow.progress safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Visionmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For workflow.progress, this is the rule to start with:
workflow.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 Visionmcp, apply this rule, and every workflow.progress call is checked against it from then on.
Questions about workflow.progress
Return compact recomputed progress without changing evidence or acceptance state. It is categorised as a Read tool in the Visionmcp MCP Server, which means it retrieves data without modifying state.
Register the Vision MCP server in PolicyLayer and add a rule for workflow.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 Visionmcp. Nothing to install.
workflow.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 workflow.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 workflow.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.
workflow.progress is provided by the Vision MCP server (joshuahickscorp/visionmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vision, and thousands of servers like it.
This server
Across the catalogue