Generate a higher-level evidence report that combines search, verification,
AI agents call evidence_report to retrieve information from Cross Validated Search without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The evidence_report tool aggregates and synthesizes information from search and verification operations without modifying, deleting, or executing arbitrary code. It retrieves and analyzes data, making it a Read category tool. Severity is low because misuse would only surface incorrect or misleading information, not cause system compromise or data loss.
From the tool's definition Tool name 'evidence_report' and description indicates it 'combines search, verification' — data retrieval and analysis operations.
Documented attack patterns abuse exactly the kind of access evidence_report gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Cross Validated Search, and nothing reaches the server without passing your rules. This is the rule we recommend for evidence_report:
{
"version": "1",
"default": "deny",
"tools": {
"evidence_report": {}
}
}evidence_report is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Generate a higher-level evidence report that combines search, verification,. It is categorised as a Read tool in the Cross Validated Search MCP Server, which means it retrieves data without modifying state.
Register the Cross Validated Search MCP server in PolicyLayer and add a rule for evidence_report: 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 Cross Validated Search. Nothing to install.
evidence_report 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_report 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_report. 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_report is provided by the Cross Validated Search MCP server (wd041216-bit/zero-api-key-web-search). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Cross Validated Search, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Cross Validated Search tools catalogued and risk-classified — across an index of 43,000+ MCP servers.