producthunt_customers

Retrieve Product Hunt product customers. Returns paginated customer products for a Product Hunt product using Product Hunt's ProductCustomersPage GraphQL operation.

SERVERCrawlora SOURCEcrawlora-mcp

Low RISK CLASS

Category Read

Parameters 41 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/crawlora-mcp/producthunt-customers.md

WHAT IT DOES

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.

RISK

Why producthunt_customers is rated Low

Even though producthunt_customers 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

RECOMMENDED RULE

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 Allowed

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

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

FAQ

Questions about producthunt_customers

What does the producthunt_customers tool do? +

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.

What parameters does producthunt_customers accept? +

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.

How do I enforce a policy on producthunt_customers? +

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.

What risk level is producthunt_customers? +

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

Can I rate-limit producthunt_customers? +

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.

How do I block producthunt_customers completely? +

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.

What MCP server provides producthunt_customers? +

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.

KEEP EXPLORING

More on Crawlora, and thousands of servers like it.

This server

All 728 Crawlora tools →

Across the catalogue

aiva_search_customers on AIVA MCP Server → The MCP Attack Database →

Guides

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