Reverse-DNS verify a bot
AI agents call verify_bot_identity to retrieve information from Mcp Bot Crawler without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries DNS records to verify bot identity information. It retrieves and validates existing data without creating, modifying, deleting, or executing any operations. The operation is informational and has no destructive or side-effect potential. Low severity because misuse would only result in DNS resolution attempts, which have minimal blast radius.
From the tool's definition Tool performs 'Reverse-DNS verify' operation on a bot identity. DNS lookups and verification checks are read-only queries that retrieve or validate data without modifying, executing code, or causing side effects.
Attacks that exploit this kind of access
Reverse-DNS verify a bot. It is categorised as a Read tool in the Mcp Bot Crawler MCP Server, which means it retrieves data without modifying state.
Register the Mcp Bot Crawler MCP server in PolicyLayer and add a rule for verify_bot_identity: 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 Mcp Bot Crawler. Nothing to install.
verify_bot_identity 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 verify_bot_identity 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 verify_bot_identity. 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.
verify_bot_identity is provided by the Mcp Bot Crawler MCP server (merulocal/hellogrowthcrmwebsite_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 →