Look up technologies and enrichment data for a single URL.
AI agents call lookup_site to retrieve information from Wappalyzer MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata and technology information about a website via the Wappalyzer API. It has no side effects, does not modify data, does not execute code, and does not affect financial state. The primary risk is information disclosure about the queried URL, which is inherently low-risk in most contexts. Confidence is high because the description clearly indicates a read-only lookup operation.
From the tool's definition Tool performs a 'Look up technologies and enrichment data for a single URL' — a query operation that retrieves and returns information about a web site without modifying, deleting, or executing anything on the target or user's system.
Attacks that exploit this kind of access
Look up technologies and enrichment data for a single URL. It is categorised as a Read tool in the Wappalyzer MCP MCP Server, which means it retrieves data without modifying state.
Register the Wappalyzer MCP server in PolicyLayer and add a rule for lookup_site: 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 Wappalyzer MCP. Nothing to install.
lookup_site 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 lookup_site 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 lookup_site. 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.
lookup_site is provided by the Wappalyzer MCP server (wappalyzer/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 →