workflow.reconstruct_from_public_evidence
Create a project and launch the autonomous public-evidence twin workflow.
This record as markdown: /tools/visionmcp/workflow.reconstruct-from-public-evidence.md
What workflow.reconstruct_from_public_evidence does on Visionmcp
AI agents use workflow.reconstruct_from_public_evidence 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_public_evidence is rated Medium
The tool creates a new project (Write) and launches an autonomous workflow. While it triggers an ongoing process, the primary action is project creation and workflow initiation rather than executing arbitrary code or commands. The 'autonomous' aspect raises the severity to medium since the spawned workflow may have broader side effects, but the description does not indicate destructive or financial operations.
From the tool's definition "Create a project and launch the autonomous public-evidence twin workflow"
Attacks that exploit this kind of access
The rule that runs workflow.reconstruct_from_public_evidence 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_public_evidence, this is the rule to start with:
workflow.reconstruct_from_public_evidence 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_public_evidence call is checked against it from then on.
Questions about workflow.reconstruct_from_public_evidence
Create a project and launch the autonomous public-evidence twin workflow. 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_public_evidence: 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_public_evidence 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_public_evidence 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_public_evidence. 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_public_evidence 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