Delete one host profile record from the profile store.
AI agents call clear_host_profile to permanently remove resources in Web Scraper — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a profile record with no undo mechanism. Although the blast radius is limited to a single host profile (not system-wide), the irreversible nature and potential for data loss if misused by an AI agent place it in the Destructive category, which ranks higher than Write or Execute.
From the tool's definition The description explicitly states 'Delete one host profile record from the profile store' — the verb 'Delete' indicates irreversible removal of stored data.
Documented attack patterns abuse exactly the kind of access clear_host_profile 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 clear_host_profile:
{
"version": "1",
"default": "deny",
"hide": [
"clear_host_profile"
]
} clear_host_profile disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete one host profile record from the profile store. It is categorised as a Destructive tool in the Web Scraper MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Web Scraper MCP server in PolicyLayer and add a rule for clear_host_profile: 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.
clear_host_profile is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the clear_host_profile 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 clear_host_profile. 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.
clear_host_profile 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.