Get scraping results from the database
AI agents call get_scraping_results to retrieve information from MCP Web Research Agent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves previously scraped data stored in SQLite. It performs a read-only operation that has no side effects and does not modify, delete, or execute any code. The low severity reflects minimal risk even if misused by an AI agent, as it can only expose data that was already collected.
From the tool's definition Tool name is 'get_scraping_results' and description states 'Get scraping results from the database' — a retrieval operation with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Get scraping results from the database. It is categorised as a Read tool in the MCP Web Research Agent MCP Server, which means it retrieves data without modifying state.
Register the MCP Web Research Agent MCP server in PolicyLayer and add a rule for get_scraping_results: 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 Research Agent. Nothing to install.
get_scraping_results 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_scraping_results 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_scraping_results. 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_scraping_results is provided by the MCP Web Research Agent MCP server (snotacusnexus/mcp-web-research-agent). 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 →