workflow.reconstruct_from_user_capture
Create a project from owner-supplied evidence and launch reference reconstruction.
This record as markdown: /tools/visionmcp/workflow.reconstruct-from-user-capture.md
What workflow.reconstruct_from_user_capture does on Visionmcp
AI agents use workflow.reconstruct_from_user_capture to create or update resources in Visionmcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Visionmcp environment.
Why workflow.reconstruct_from_user_capture is rated Medium
This tool creates a new project based on user input, which is a reversible write operation. It does not execute arbitrary code or external operations (Execute), does not permanently delete data (Destructive), involves no financial transactions (Financial), and is not merely a read operation.
From the tool's definition Tool description states 'Create a project from owner-supplied evidence and launch reference reconstruction.' The verb 'Create' indicates data creation; 'from owner-supplied evidence' suggests user-provided input is processed to build a new project artifact.
Attacks that exploit this kind of access
The rule that runs workflow.reconstruct_from_user_capture 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_from_user_capture, this is the rule to start with:
workflow.reconstruct_from_user_capture stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_from_user_capture call is checked against it from then on.
Questions about workflow.reconstruct_from_user_capture
Create a project from owner-supplied evidence and launch reference reconstruction. It is categorised as a Write tool in the Visionmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vision MCP server in PolicyLayer and add a rule for workflow.reconstruct_from_user_capture: 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_from_user_capture is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the workflow.reconstruct_from_user_capture 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_from_user_capture. 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_from_user_capture 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