Check the operational status of ScamVerify API services. Returns health status for each component (phone, URL, text, email, document lookups, database, AI inference). No authentication required.
AI agents call get_status 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 retrieves operational/health information about API components with no ability to modify, execute, or delete anything. It is a standard read-only status check endpoint. Low severity because even if misused by an agent, the only information disclosed is service availability, which has minimal blast radius.
From the tool's definition Tool name 'get_status' and description states it 'Check[s] the operational status' and 'Returns health status for each component'. No side effects mentioned; purely informational query of service state.
Attacks that exploit this kind of access
Check the operational status of ScamVerify API services. Returns health status for each component (phone, URL, text, email, document lookups, database, AI inference). No authentication required. 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 get_status: 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.
get_status 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 get_status 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 get_status. 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.
get_status 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.
get_status is one line of ScamVerify's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →