list_launches
List live product launches on FastDrop, ranked by votes. Each product may include an MCP endpoint URL, mcpVerified (whether FastDrop probe succeeded), and mcpAuthRequired when the endpoint answered 401/403.
This record as markdown: /tools/dev-fastdrop-fastdrop/list-launches.md
What list_launches does on Fastdrop
AI agents call list_launches to retrieve information from Fastdrop 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 |
|---|---|---|---|
limit | number | — | Max results, 1-50, default 20 |
window | string | — | Rank by votes cast in this window (UTC). Default all-time. |
Parameters from the server's own tool schema.
Why list_launches is rated Low
Even though list_launches 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 list_launches safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Fastdrop, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_launches, this is the rule to start with:
list_launches 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 Fastdrop, apply this rule, and every list_launches call is checked against it from then on.
Questions about list_launches
List live product launches on FastDrop, ranked by votes. Each product may include an MCP endpoint URL, mcpVerified (whether FastDrop probe succeeded), and mcpAuthRequired when the endpoint answered 401/403. It is categorised as a Read tool in the Fastdrop MCP Server, which means it retrieves data without modifying state.
list_launches accepts 2 parameters: limit, window. The full parameter table on this page comes from the server's own tool schema.
Register the Fastdrop MCP server in PolicyLayer and add a rule for list_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 Fastdrop. Nothing to install.
list_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 list_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 list_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.
list_launches is provided by the Fastdrop MCP server (https://fastdrop.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Fastdrop, and thousands of servers like it.
This server
Across the catalogue