vision.build_reconstruction_portfolio
Run requested reconstruction backends and seal a ReconstructionPortfolio.
This record as markdown: /tools/visionmcp/vision.build-reconstruction-portfolio.md
What vision.build_reconstruction_portfolio does on Visionmcp
AI agents invoke vision.build_reconstruction_portfolio 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 vision.build_reconstruction_portfolio is rated High
This tool executes reconstruction backends, which are external operations whose effects depend on the arguments provided (which backends are requested, what data they process). Execution of backends can produce side effects that are difficult to predict or undo without additional context.
From the tool's definition Tool description states 'Run requested reconstruction backends' — the verb 'Run' indicates execution of backend processes. 'Seal a ReconstructionPortfolio' suggests state changes and finalization of outputs from those backends.
Attacks that exploit this kind of access
The rule that runs vision.build_reconstruction_portfolio 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.build_reconstruction_portfolio, this is the rule to start with:
vision.build_reconstruction_portfolio 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 vision.build_reconstruction_portfolio call is checked against it from then on.
Questions about vision.build_reconstruction_portfolio
Run requested reconstruction backends and seal a ReconstructionPortfolio. 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 vision.build_reconstruction_portfolio: 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.build_reconstruction_portfolio 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 vision.build_reconstruction_portfolio 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.build_reconstruction_portfolio. 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.build_reconstruction_portfolio 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