producthunt_leaderboard
Retrieve Product Hunt leaderboard. Fetches Product Hunt leaderboard data for daily, weekly, monthly, or yearly scopes via Product Hunt GraphQL.
This record as markdown: /tools/crawlora-mcp/producthunt-leaderboard.md
What producthunt_leaderboard does on Crawlora
AI agents call producthunt_leaderboard 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 |
|---|---|---|---|
day | integer | — | Daily day override |
date | string | — | Anchor date in YYYY-MM-DD format. Used to derive missing year/month/day/week values. |
week | integer | — | Weekly ISO week override |
year | integer | — | Leaderboard year override |
month | integer | — | Daily/monthly month override |
order | string | — | Ranking order override. Defaults to scope rank enum. |
scope | string | — | Leaderboard scope: daily, weekly, monthly, yearly |
cursor | string | — | Pagination cursor |
featured | boolean | — | Featured products only |
Parameters from the server's own tool schema.
Why producthunt_leaderboard is rated Low
Even though producthunt_leaderboard 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 producthunt_leaderboard 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_leaderboard, this is the rule to start with:
producthunt_leaderboard 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_leaderboard call is checked against it from then on.
Questions about producthunt_leaderboard
Retrieve Product Hunt leaderboard. Fetches Product Hunt leaderboard data for daily, weekly, monthly, or yearly scopes via Product Hunt GraphQL. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
producthunt_leaderboard accepts 9 parameters: day, date, week, year, month, order, scope, cursor, featured. 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_leaderboard: 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_leaderboard 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_leaderboard 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_leaderboard. 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_leaderboard 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