list_work_launches

SERVERAdrata SOURCE@adrata/adrata-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adrata-adrata-mcp/list-work-launches.md

WHAT IT DOES

What list_work_launches does on Adrata

AI agents call list_work_launches to retrieve information from Adrata without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_work_launches is rated Low

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

RECOMMENDED RULE

The rule that runs list_work_launches safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Adrata, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_work_launches, this is the rule to start with:

list_work_launches Allowed

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Adrata, apply this rule, and every list_work_launches call is checked against it from then on.

FAQ

Questions about list_work_launches

What does the list_work_launches tool do? +

List the launches in the workspace — each a named, dated set of cards that must ship together, with its readiness as COUNTS (cards, p0/p1/p2/unranked, and how many sit in each stage). A launch is a lens over the boards, not a board: its cards stay on their own boards. Start here; get_work_launch needs an id from this list. It is categorised as a Read tool in the Adrata MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_work_launches? +

Register the Adrata MCP server in PolicyLayer and add a rule for list_work_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 Adrata. Nothing to install.

What risk level is list_work_launches? +

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

Can I rate-limit list_work_launches? +

Yes. Add a rate_limit block to the list_work_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.

How do I block list_work_launches completely? +

Set action: deny in the PolicyLayer policy for list_work_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.

What MCP server provides list_work_launches? +

list_work_launches is provided by the Adrata MCP server (@adrata/adrata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Adrata, and thousands of servers like it.

This server

All 395 Adrata tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

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