evidence.resolve_conflicts
Detect source variants that conflict with the canonical project identity.
This record as markdown: /tools/visionmcp/evidence.resolve-conflicts.md
What evidence.resolve_conflicts does on Visionmcp
AI agents call evidence.resolve_conflicts to retrieve information from Visionmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why evidence.resolve_conflicts is rated Low
This tool performs conflict detection and analysis, which is a read-only operation that retrieves or queries data about source variants and their relationship to a canonical project identity. There is no indication that it modifies, creates, deletes, executes code, or moves financial resources. The blast radius of misuse is limited to information disclosure about conflicts.
From the tool's definition Tool description states 'Detect source variants that conflict with the canonical project identity' — uses language of detection and analysis without modifying, creating, or deleting resources. The verb 'detect' indicates a query or inspection operation.
Attacks that exploit this kind of access
The rule that runs evidence.resolve_conflicts 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 evidence.resolve_conflicts, this is the rule to start with:
evidence.resolve_conflicts is read-only, so it stays allowed. 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 evidence.resolve_conflicts call is checked against it from then on.
Questions about evidence.resolve_conflicts
Detect source variants that conflict with the canonical project identity. It is categorised as a Read tool in the Visionmcp MCP Server, which means it retrieves data without modifying state.
Register the Vision MCP server in PolicyLayer and add a rule for evidence.resolve_conflicts: 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.
evidence.resolve_conflicts is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the evidence.resolve_conflicts 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 evidence.resolve_conflicts. 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.
evidence.resolve_conflicts 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