Detect tracking scripts and privacy-related elements
AI agents call detect_tracking 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 detection and analysis of existing tracking elements—a passive information gathering operation with no side effects. It reads and reports on tracking data but does not modify, delete, execute code, or perform financial operations. The severity is low because misuse would only result in incorrect detection reporting, with no ability to cause harm beyond false positives/negatives in analysis.
From the tool's definition Tool name 'detect_tracking' and description 'Detect tracking scripts and privacy-related elements' indicate the tool analyzes and retrieves information about tracking mechanisms on web pages without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access detect_tracking 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_tracking:
{
"version": "1",
"default": "deny",
"tools": {
"detect_tracking": {}
}
}detect_tracking 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 tracking scripts and privacy-related elements. 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_tracking: 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_tracking 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_tracking 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_tracking. 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_tracking 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.