target.resolve
Resolve and persist one canonical variant without merging incompatible evidence.
This record as markdown: /tools/visionmcp/target.resolve.md
What target.resolve does on Visionmcp
AI agents use target.resolve 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 target.resolve is rated Medium
The tool resolves a canonical variant and persists it, which is a write operation creating or updating stored state. It is not destructive (it explicitly avoids merging incompatible evidence rather than deleting it), not financial, and not merely reading data. Severity is medium because persisting an incorrect canonical variant could corrupt downstream pipeline state, but the action appears targeted and bounded.
From the tool's definition "Resolve and persist one canonical variant" — the word 'persist' confirms a write/save operation to storage.
Attacks that exploit this kind of access
The rule that runs target.resolve 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 target.resolve, this is the rule to start with:
target.resolve 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 target.resolve call is checked against it from then on.
Questions about target.resolve
Resolve and persist one canonical variant without merging incompatible evidence. 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 target.resolve: 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.
target.resolve 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 target.resolve 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 target.resolve. 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.
target.resolve 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