Analyze a document image for scam indicators. Upload a photo of a suspicious letter, court notice, receipt, invoice, or other document. Uses vision AI to extract entities (addresses, officials, citations, phone numbers) and verifies them against government databases. Returns risk score, verdict, ...
AI agents call check_document to retrieve information from ScamVerify without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads document content, performs threat intelligence lookups, and returns analysis results. It retrieves data from intelligence records and government databases to assess scam risk, but does not create, modify, delete, or execute any operations.
From the tool's definition Tool performs document analysis and verification against databases, extracting entities and returning risk scores and verdicts.
Attacks that exploit this kind of access
Analyze a document image for scam indicators. Upload a photo of a suspicious letter, court notice, receipt, invoice, or other document. Uses vision AI to extract entities (addresses, officials, citations, phone numbers) and verifies them against government databases. Returns risk score, verdict, red flags, and entity verification results. It is categorised as a Read tool in the ScamVerify MCP Server, which means it retrieves data without modifying state.
Register the ScamVerify MCP server in PolicyLayer and add a rule for check_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 ScamVerify. Nothing to install.
check_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 check_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 check_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.
check_document is provided by the ScamVerify MCP server (scamverifyai/scamverify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →