recon.repair
Propose a supported repair; a separate named approval is required before application.
This record as markdown: /tools/visionmcp/recon.repair.md
What recon.repair does on Visionmcp
AI agents use recon.repair 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 recon.repair is rated Medium
The tool proposes a repair but does not apply it — actual changes require a separate approval step. This is a Write-category action (creates/modifies data) but is gated by a review step, reducing the blast radius. Since no irreversible deletion or execution of code is described, Write is the most applicable category.
From the tool's definition 'Propose a supported repair; a separate named approval is required before application'
Attacks that exploit this kind of access
The rule that runs recon.repair 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 recon.repair, this is the rule to start with:
recon.repair 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 recon.repair call is checked against it from then on.
Questions about recon.repair
Propose a supported repair; a separate named approval is required before application. 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 recon.repair: 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.
recon.repair 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 recon.repair 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 recon.repair. 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.
recon.repair 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