Get basic information about a webpage (title, element counts, structure)
AI agents call get_page_info to retrieve information from MCP Web Scraper without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries metadata about a webpage without any side effects, state changes, or external operations. It falls squarely within the Read category as a data retrieval function. The low severity reflects that extracting public webpage metadata poses minimal risk even if misused by an AI agent.
From the tool's definition Tool description states it 'Get[s] basic information about a webpage (title, element counts, structure)' — purely informational retrieval with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get basic information about a webpage (title, element counts, structure). It is categorised as a Read tool in the MCP Web Scraper MCP Server, which means it retrieves data without modifying state.
Register the MCP Web Scraper MCP server in PolicyLayer and add a rule for get_page_info: 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 Web Scraper. Nothing to install.
get_page_info 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_page_info 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_page_info. 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_page_info is provided by the MCP Web Scraper MCP server (navin4078/mcp-web-scraper). 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 →