datasets_trustmrr_facets
Facet the TrustMRR dataset. Returns terms-aggregation counts for one facet of the TrustMRR dataset, scoped to the same filters as search. Facet enum: category, country, payment_provider, target_audience, business_type, tech, channels, listing_tier, status, on_sale, is_sponsored, tags.
This record as markdown: /tools/crawlora-mcp/datasets-trustmrr-facets.md
What datasets_trustmrr_facets does on Crawlora
AI agents call datasets_trustmrr_facets 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 | — | Full-text query, max 256 characters |
facet | string | Yes | Facet enum: category, country, payment_provider, target_audience, business_type, tech, channels, listing_tier, status, on_sale, is_sponsored, tags |
country | string | — | Exact ISO country-code filter, max 128 characters |
min_mrr | number | — | Minimum verified MRR in USD |
on_sale | boolean | — | Filter for startups currently listed for sale |
category | string | — | Exact category filter, max 128 characters |
payment_provider | string | — | Payment-provider filter, max 128 characters |
Parameters from the server's own tool schema.
Why datasets_trustmrr_facets is rated Low
Even though datasets_trustmrr_facets 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.
Attacks that exploit this kind of access
The rule that runs datasets_trustmrr_facets 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_trustmrr_facets, this is the rule to start with:
datasets_trustmrr_facets is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crawlora, apply this rule, and every datasets_trustmrr_facets call is checked against it from then on.
Questions about datasets_trustmrr_facets
Facet the TrustMRR dataset. Returns terms-aggregation counts for one facet of the TrustMRR dataset, scoped to the same filters as search. Facet enum: category, country, payment_provider, target_audience, business_type, tech, channels, listing_tier, status, on_sale, is_sponsored, tags. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
datasets_trustmrr_facets accepts 7 parameters: q, facet, country, min_mrr, on_sale, category, payment_provider. Required: facet. The full parameter table on this page comes from the server's own tool schema.
Register the Crawlora MCP server in PolicyLayer and add a rule for datasets_trustmrr_facets: 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.
datasets_trustmrr_facets 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 datasets_trustmrr_facets 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 datasets_trustmrr_facets. 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.
datasets_trustmrr_facets 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.
More on Crawlora, and thousands of servers like it.
This server
Across the catalogue