vision.progress
Return compact perception progress and evidence counts.
This record as markdown: /tools/visionmcp/vision.progress.md
What vision.progress does on Visionmcp
AI agents call vision.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 vision.progress is rated Low
This tool retrieves status information and metrics about perception progress and evidence. It performs no data modification, deletion, code execution, or financial operations. The read-only nature (returning/reporting data) places it firmly in the Read category with low severity.
From the tool's definition Tool name 'progress' with description 'Return compact perception progress and evidence counts' indicates data retrieval only. The verb 'Return' and the noun 'counts' suggest querying state without modification.
Attacks that exploit this kind of access
The rule that runs vision.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 vision.progress, this is the rule to start with:
vision.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 vision.progress call is checked against it from then on.
Questions about vision.progress
Return compact perception progress and evidence counts. 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 vision.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.
vision.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 vision.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 vision.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.
vision.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