AI agents call detect_language to retrieve information from MCP Web Scrape without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs content analysis to identify the language of a webpage. It retrieves and examines existing data without creating, modifying, deleting, or executing any operations. It has no side effects and poses minimal security risk—language detection is a passive read operation commonly used for content classification and accessibility.
From the tool's definition Tool name 'detect_language' and description 'Detect the primary language of web page content' indicate analysis and retrieval of information with no modification, deletion, or code execution.
Documented attack patterns abuse exactly the kind of access detect_language gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Web Scrape, and nothing reaches the server without passing your rules. This is the rule we recommend for detect_language:
{
"version": "1",
"default": "deny",
"tools": {
"detect_language": {}
}
}detect_language 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.
Detect the primary language of web page content. It is categorised as a Read tool in the MCP Web Scrape MCP Server, which means it retrieves data without modifying state.
Register the MCP Web Scrape MCP server in PolicyLayer and add a rule for detect_language: 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 Scrape. Nothing to install.
detect_language 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 detect_language 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 detect_language. 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.
detect_language is provided by the MCP Web Scrape MCP server (mukul975/mcp-web-scrape). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Web Scrape, 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.
48 MCP Web Scrape tools catalogued and risk-classified — across an index of 43,000+ MCP servers.