evidence.discover
Execute reviewed search queries and register results with unresolved source rights.
This record as markdown: /tools/visionmcp/evidence.discover.md
What evidence.discover does on Visionmcp
AI agents invoke evidence.discover 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 evidence.discover is rated High
The tool executes search queries and registers results, which constitutes executing external operations whose effects depend on query arguments. While 'reviewed' suggests some safeguards, the registration of results modifies system state. This is Execute rather than Read (which would be passive retrieval) because it both executes queries and persists results.
From the tool's definition Tool description states 'Execute reviewed search queries' and 'register results' — indicates execution of search operations and registration/modification of results in a system.
Attacks that exploit this kind of access
The rule that runs evidence.discover 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.discover, this is the rule to start with:
evidence.discover 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 evidence.discover call is checked against it from then on.
Questions about evidence.discover
Execute reviewed search queries and register results with unresolved source rights. 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 evidence.discover: 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.discover 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 evidence.discover 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.discover. 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.discover 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