wes_list_tasks
AI agents call wes_list_tasks to retrieve information from NGS360 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
List operations retrieve and query existing data with no side effects. The empty description reduces confidence slightly, but the semantic meaning of 'list' in the name strongly indicates a Read operation. This would have low severity since listing tasks poses minimal risk—it reveals information but cannot modify or delete data, execute code, or commit financial obligations.
From the tool's definition Tool name 'wes_list_tasks' contains the verb 'list', which indicates retrieval or enumeration of data without modification. The 'WES' prefix suggests Workflow Execution Service, a standard bioinformatics API pattern for querying task status.
Attacks that exploit this kind of access
wes_list_tasks. It is categorised as a Read tool in the NGS360 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the NGS360 MCP Server MCP server in PolicyLayer and add a rule for wes_list_tasks: 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 NGS360 MCP Server. Nothing to install.
wes_list_tasks 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 wes_list_tasks 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 wes_list_tasks. 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.
wes_list_tasks is provided by the NGS360 MCP Server MCP server (ngs360/mcp-server). 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 →