datasets_techstack_search

SERVERCrawlora SOURCEcrawlora-mcp

Low RISK CLASS

Category Read

Parameters 120 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What datasets_techstack_search does on Crawlora

AI agents call datasets_techstack_search 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
`q`	string	—	Substring match on the site domain, max 256 characters
`cdn`	string	—	Exact CDN / hosting filter, e.g. Cloudflare, Fastly, Vercel
`cms`	string	—	Exact CMS filter, e.g. WordPress, Shopify, Webflow
`not`	array	—	Repeatable exact technology name the site must NOT use (excludes)
`tld`	string	—	Exact top-level-domain filter, e.g. com, org, io
`page`	integer	—	Page number, defaults to 1
`sort`	string	—	Sort enum: relevance, rank_asc, tech_count_desc, domain_asc, crawled_desc
`any_of`	array	—	Repeatable exact technology name; the site must use at least one (OR)
`run_id`	string	—	Scan run id; defaults to the latest run
`category`	string	—	Exact category filter, e.g. Ecommerce, CMS, Analytics, Payment, CDN
`ecommerce`	string	—	Exact e-commerce platform filter, e.g. Shopify, WooCommerce, Magento
`page_size`	integer	—	Page size, defaults to 20 and maxes at 100; page * page_size must be <= 10000

Parameters from the server's own tool schema.

RISK

Why datasets_techstack_search is rated Low

Even though datasets_techstack_search only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsHigh parameter count (20 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs datasets_techstack_search 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 datasets_techstack_search, this is the rule to start with:

datasets_techstack_search Allowed

datasets_techstack_search 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": {
    "datasets_techstack_search": {}
  }
}

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 datasets_techstack_search call is checked against it from then on.

FAQ

Questions about datasets_techstack_search

What does the datasets_techstack_search tool do? +

Search the website tech-stack dataset. Searches the website tech-stack index (dataset id enum value techstack) — one record per site listing the web technologies it is built with (frameworks, CMS, e-commerce, analytics, CDNs, servers, and more), BuiltWith / Wappalyzer-style. The reverse-index filters are the point: repeat technology to require several at once (AND), any_of to match at least one (OR), and not to exclude — e.g. sites on Shopify and Klaviyo but not Recharge. Sort enum: relevance, rank_asc, tech_count_desc, domain_asc, crawled_desc. render_tier enum: http, browser. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.

What parameters does datasets_techstack_search accept? +

datasets_techstack_search accepts 12 parameters: q, cdn, cms, not, tld, page, sort, any_of, run_id, category, ecommerce, page_size. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on datasets_techstack_search? +

Register the Crawlora MCP server in PolicyLayer and add a rule for datasets_techstack_search: 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 datasets_techstack_search? +

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

Can I rate-limit datasets_techstack_search? +

Yes. Add a rate_limit block to the datasets_techstack_search 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 datasets_techstack_search completely? +

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

datasets_techstack_search 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

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_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 →