Set active host routing profile from JSON payload (admin override).
AI agents use set_host_profile to create or update resources in Web Scraper — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Web Scraper environment.
This tool modifies the active host routing configuration via a JSON payload. 'Admin override' implies elevated privilege changes to routing behavior, which is a high-severity write operation that could redirect all web scraping/crawling traffic through arbitrary hosts. While it modifies configuration (Write), it could be misused to intercept or redirect traffic.
From the tool's definition Set active host routing profile from JSON payload (admin override)
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access set_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 set_host_profile:
{
"version": "1",
"default": "deny",
"tools": {
"set_host_profile": {
"limits": [
{
"counter": "set_host_profile_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} set_host_profile stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Set active host routing profile from JSON payload (admin override). It is categorised as a Write tool in the Web Scraper MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Web Scraper MCP server in PolicyLayer and add a rule for set_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.
set_host_profile is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_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 set_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.
set_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.