Return host profile learning store (all hosts or one host).
AI agents call get_host_profiles to retrieve information from 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 host profile data from a learning store without modifying, executing, or deleting anything. It queries existing profile information to support the web scraping workflow. Low severity because the blast radius of misuse is limited to unauthorized data disclosure of profile metadata, not destructive actions or code execution.
From the tool's definition Tool name 'get_host_profiles' and description 'Return host profile learning store' indicate a retrieval operation with no modification capability. The verb 'Return' and absence of any mutation language confirm read-only semantics.
Documented attack patterns abuse exactly the kind of access get_host_profiles gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Web Scraper, and nothing reaches the server without passing your rules. This is the rule we recommend for get_host_profiles:
{
"version": "1",
"default": "deny",
"tools": {
"get_host_profiles": {}
}
}get_host_profiles is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Return host profile learning store (all hosts or one host). It is categorised as a Read tool in the Web Scraper MCP Server, which means it retrieves data without modifying state.
Register the Web Scraper MCP server in PolicyLayer and add a rule for get_host_profiles: 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 Web Scraper. Nothing to install.
get_host_profiles 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_host_profiles 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_host_profiles. 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_host_profiles is provided by the Web Scraper MCP server (imyourboyroy/webscrapertoolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Web Scraper, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
62 Web Scraper tools catalogued and risk-classified — across an index of 43,000+ MCP servers.