Get today's and recent top Product Hunt launches — new product and startup launches. Use this to see what launched today/recently or which products are trending. Returns name, tagline, vote/comment counts, URLs, and topics. Example: top_launches({ first: 10, order: "RANKING" })
AI agents call top_launches to retrieve information from Mcp Producthunt without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
first | number | — | Number of launches to return (default 10, max 20) |
order | string | — | Sort order: "RANKING" (default — trending), "VOTES" (most upvoted), or "NEWEST" (most recently launched) |
_apiKey | string | — | Optional — your own Product Hunt developer token for higher limits; omit to use the shared Pipeworx key. |
Parameters from the server's own tool schema.
This tool performs a straightforward data retrieval operation against the Product Hunt API. It returns publicly available information about product launches without creating, modifying, deleting, or executing any operations. No financial transactions, destructive actions, or code execution are involved.
From the tool's definition Tool retrieves Product Hunt launch data including names, taglines, vote counts, URLs, and topics. The description emphasizes 'Get' and 'see what launched', indicating query/retrieval operations with no modification or side effects.
Attacks that exploit this kind of access
Get today's and recent top Product Hunt launches — new product and startup launches. Use this to see what launched today/recently or which products are trending. Returns name, tagline, vote/comment counts, URLs, and topics. Example: top_launches({ first: 10, order: "RANKING" }). It is categorised as a Read tool in the Mcp Producthunt MCP Server, which means it retrieves data without modifying state.
top_launches accepts 3 parameters: first, order, _apiKey. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Producthunt MCP server in PolicyLayer and add a rule for top_launches: 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 Mcp Producthunt. Nothing to install.
top_launches 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 top_launches 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 top_launches. 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.
top_launches is provided by the Mcp Producthunt MCP server (https://gateway.pipeworx.io/producthunt/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →