List all pipeline run directories in the logs folder, newest first.
AI agents call list_runs to retrieve information from Tacc Mcp Bio without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a directory listing operation with no side effects. It retrieves metadata about existing pipeline runs for informational purposes only. The severity is low because misuse (e.g., an agent listing runs repeatedly) would cause minimal harm — no data is modified, deleted, or executed. The confidence is high because the description clearly indicates a passive enumeration function.
From the tool's definition Tool name is 'list_runs' and description states 'List all pipeline run directories in the logs folder' — a read-only query operation that retrieves and displays existing data without modification or deletion.
Attacks that exploit this kind of access
List all pipeline run directories in the logs folder, newest first. It is categorised as a Read tool in the Tacc Mcp Bio MCP Server, which means it retrieves data without modifying state.
Register the Tacc Mcp Bio 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 Tacc Mcp Bio. Nothing to install.
list_runs 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_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.
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.
list_runs is provided by the Tacc Mcp Bio MCP server (narasimhan-lab/tacc-mcp-bio). 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 →