list_runs

List run records, filterable by agent and paginated. Returns run status, trigger source and the associated agent.

SERVERA2wave SOURCELilithGames/a2wave

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/a2wave/list-runs.md

WHAT IT DOES

What list_runs does on A2wave

AI agents call list_runs to retrieve information from A2wave 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_runs is rated Low

Tool retrieves historical run data without modifying or executing any operations.

From the tool's definition List run records, filterable by agent and paginated. Returns run status.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_runs safely

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

list_runs Allowed

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

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

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

FAQ

Questions about list_runs

What does the list_runs tool do? +

List run records, filterable by agent and paginated. Returns run status, trigger source and the associated agent. It is categorised as a Read tool in the A2wave MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_runs? +

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

What risk level is list_runs? +

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

Can I rate-limit list_runs? +

Yes. Add a rate_limit block to the list_runs 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_runs completely? +

Set action: deny in the PolicyLayer policy for list_runs. 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_runs? +

list_runs is provided by the A2wave MCP server (LilithGames/a2wave). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on A2wave, and thousands of servers like it.

This server

All 22 A2wave 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 →