Detect content type of URL (HTML, PDF, image, etc.).
AI agents call detect_content_type 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 performs a non-destructive inspection of URL content type, analogous to reading HTTP headers. It retrieves information without creating, modifying, deleting, or executing operations. The low severity reflects minimal risk even if an AI agent misuses it—detection errors have no side effects beyond potentially incorrect routing logic.
From the tool's definition Tool name 'detect_content_type' and description 'Detect content type of URL' indicate a query operation that retrieves metadata about a resource without modifying or executing code. No side effects are produced.
Documented attack patterns abuse exactly the kind of access detect_content_type 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 detect_content_type:
{
"version": "1",
"default": "deny",
"tools": {
"detect_content_type": {}
}
}detect_content_type 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 content type of URL (HTML, PDF, image, etc.). 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 detect_content_type: 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.
detect_content_type 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_content_type 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_content_type. 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_content_type 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.