AI agents use configure_stealth 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 configuration/settings of the scraper (stealth mode, robots.txt compliance). It writes/updates configuration state rather than reading data or executing actions. The severity is medium because misconfiguration could enable bypassing anti-bot measures or ignoring robots.txt, facilitating unauthorized scraping — but the tool itself only changes settings reversibly.
From the tool's definition Configure stealth mode and robots.txt compliance
Documented attack patterns abuse exactly the kind of access configure_stealth 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 configure_stealth:
{
"version": "1",
"default": "deny",
"tools": {
"configure_stealth": {
"limits": [
{
"counter": "configure_stealth_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} configure_stealth 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.
Configure stealth mode and robots.txt compliance. 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 configure_stealth: 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.
configure_stealth 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 configure_stealth 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 configure_stealth. 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.
configure_stealth 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.