web_techstack

SERVERCrawlora SOURCEcrawlora-mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/crawlora-mcp/web-techstack.md

WHAT IT DOES

What web_techstack does on Crawlora

AI agents call web_techstack to retrieve information from Crawlora without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`request`	object	Yes	Target URL (and optional render strategy)

Parameters from the server's own tool schema.

RISK

Why web_techstack is rated Low

This tool retrieves and analyzes publicly available information about website technology stacks. It performs passive reconnaissance by fetching public URLs and analyzing their responses to identify technologies used. There are no side effects, no data modification, no code execution on the target system, and no destructive or financial operations. It is purely informational/analytical, fitting the Read category.

From the tool's definition Fetches a public URL and fingerprints the web technologies it is built with — a BuiltWith / Wappalyzer-style detector. Returns a list of detected `technologies` with their `categories`, `confidence`, `version`, and `evidence`.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs web_techstack safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Crawlora, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For web_techstack, this is the rule to start with:

web_techstack Allowed

web_techstack is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "web_techstack": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Crawlora, apply this rule, and every web_techstack call is checked against it from then on.

FAQ

Questions about web_techstack

What does the web_techstack tool do? +

Tech stack — detect what a website is built with. Fetches a public URL and fingerprints the web technologies it is built with — a BuiltWith / Wappalyzer-style detector. Returns a list of detected technologies, each with its categories, a confidence (high, medium, low), an optional version, and the evidence that matched. Covers JavaScript frameworks and libraries (React, Vue.js, Angular, Svelte, jQuery), web frameworks / static site generators (Next.js, Nuxt.js, Gatsby, Remix, SvelteKit, Astro, Hugo), CMS and website builders (WordPress, Drupal, Joomla, Ghost, Wix, Squarespace, Webflow), e-commerce (Shopify, WooCommerce, Magento, BigCommerce), analytics, ad pixels, and tag managers (Google Analytics, Google Tag Manager, Meta Pixel, LinkedIn, Bing, TikTok/Pinterest/Reddit pixels, Segment, Hotjar, Microsoft Clarity), CDNs, UI frameworks and fonts, payments (Stripe, PayPal, Klarna), live chat, marketing automation, A/B testing, consent management, CAPTCHAs (reCAPTCHA, hCaptcha, Turnstile), video, and search. It also inspects response headers (from a plain HTTP fetch) to identify the web server (nginx, Apache, IIS), the CDN / hosting provider (Cloudflare, CloudFront, Fastly, Vercel, Netlify), and the server-side language / framework (PHP, ASP.NET, Ruby on Rails, Django, Laravel, Express). Results are directional, not exhaustive. The render fetch strategy is one of browser (headless browser that executes JavaScript — the default, so client-injected scripts like analytics, tag managers and pixels are detected), auto (Chrome-impersonated HTTP, escalating to a real browser only when blocked or JS-rendered), or http (HTTP only, no JavaScript — fastest, but sees only the server HTML); defaults to browser. Only public pages are supported; respect each site's terms of use and robots directives. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.

What parameters does web_techstack accept? +

web_techstack accepts 1 parameter: request. Required: request. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on web_techstack? +

Register the Crawlora MCP server in PolicyLayer and add a rule for web_techstack: 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 Crawlora. Nothing to install.

What risk level is web_techstack? +

web_techstack is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit web_techstack? +

Yes. Add a rate_limit block to the web_techstack 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.

How do I block web_techstack completely? +

Set action: deny in the PolicyLayer policy for web_techstack. 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.

What MCP server provides web_techstack? +

web_techstack is provided by the Crawlora MCP server (crawlora-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Crawlora, and thousands of servers like it.

This server

All 728 Crawlora tools →

Across the catalogue

web_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →