producthunt_customers
Retrieve Product Hunt product customers. Returns paginated customer products for a Product Hunt product using Product Hunt's ProductCustomersPage GraphQL operation.
This record as markdown: /tools/crawlora-mcp/producthunt-customers.md
What producthunt_customers does on Crawlora
AI agents call producthunt_customers 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 |
|---|---|---|---|
id | string | Yes | Product Hunt slug |
page | integer | — | Page number |
order | string | — | Product Hunt customers order |
page_size | integer | — | Results per page |
Parameters from the server's own tool schema.
Why producthunt_customers is rated Low
This tool retrieves/queries customer data from Product Hunt via a GraphQL read operation. It has no side effects—it does not create, modify, delete, execute code, or move money. The verb 'Retrieve' and the read-only nature of a GraphQL query operation confirm this is a Read category tool. Severity is low because access to customer lists on a public platform carries minimal blast radius if misused by an AI agent.
From the tool's definition Retrieve Product Hunt product customers. Returns paginated customer products... using Product Hunt's ProductCustomersPage GraphQL operation.
Attacks that exploit this kind of access
The rule that runs producthunt_customers 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 producthunt_customers, this is the rule to start with:
producthunt_customers 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 producthunt_customers call is checked against it from then on.
Questions about producthunt_customers
Retrieve Product Hunt product customers. Returns paginated customer products for a Product Hunt product using Product Hunt's ProductCustomersPage GraphQL operation. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
producthunt_customers accepts 4 parameters: id, page, order, page_size. Required: id. 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 producthunt_customers: 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.
producthunt_customers 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 producthunt_customers 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 producthunt_customers. 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.
producthunt_customers 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