workflow.reconstruct_product
Queue the complete staged reconstruction/audit workflow and retain all blockers.
This record as markdown: /tools/visionmcp/workflow.reconstruct-product.md
What workflow.reconstruct_product does on Visionmcp
AI agents invoke workflow.reconstruct_product to trigger actions in Visionmcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why workflow.reconstruct_product is rated High
The tool triggers a multi-stage workflow execution (queuing and running a complete reconstruction/audit pipeline). This is an Execute-class action as it initiates external operations whose effects depend on the workflow's configuration and state. 'Retain all blockers' suggests it manages workflow state beyond simple reads or writes.
From the tool's definition Queue the complete staged reconstruction/audit workflow and retain all blockers
Attacks that exploit this kind of access
The rule that runs workflow.reconstruct_product 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.reconstruct_product, this is the rule to start with:
workflow.reconstruct_product stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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.reconstruct_product call is checked against it from then on.
Questions about workflow.reconstruct_product
Queue the complete staged reconstruction/audit workflow and retain all blockers. It is categorised as a Execute tool in the Visionmcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Vision MCP server in PolicyLayer and add a rule for workflow.reconstruct_product: 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.reconstruct_product is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the workflow.reconstruct_product 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.reconstruct_product. 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.reconstruct_product 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.
Across the catalogue