Fact-check an entire document (AI-generated report, competitive analysis, market research, news article). Extracts every atomic claim and verifies each against live web sources. Returns a per-claim verification status with sources, NLI scores, and an overall A-F grade. Use for auditing the accura...
Risk signalsBulk/mass operation — affects multiple targets
Part of the BrowseAI Dev server.
Free to start. No card required.
AI agents call browse_verify_document to retrieve information from BrowseAI Dev without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though browse_verify_document only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"browse_verify_document": {}
}
}See the full BrowseAI Dev policy for all 14 tools.
These attack patterns abuse exactly the kind of access browse_verify_document gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Fact-check an entire document (AI-generated report, competitive analysis, market research, news article). Extracts every atomic claim and verifies each against live web sources. Returns a per-claim verification status with sources, NLI scores, and an overall A-F grade. Use for auditing the accuracy of long-form content from other AI agents.. It is categorised as a Read tool in the BrowseAI Dev MCP Server, which means it retrieves data without modifying state.
Register the BrowseAI Dev MCP server in PolicyLayer and add a rule for browse_verify_document: 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 BrowseAI Dev. Nothing to install.
browse_verify_document 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 browse_verify_document 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 browse_verify_document. 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.
browse_verify_document is provided by the BrowseAI Dev MCP server (browseai-dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 BrowseAI Dev tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.