wes_get_run_status
AI agents call wes_get_run_status 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.
The tool name strongly indicates a read operation that queries the status of a sequencing run. No side effects are implied. While the description is missing (reducing confidence slightly), the naming pattern is clear and consistent with read-only operations in genomics workflows. Status queries have minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'wes_get_run_status' indicates a status query operation; 'get' and 'status' are read verbs. Description is empty, but naming convention and sibling tools (create_*, add_*, etc.) suggest this retrieves run status without modification.
Attacks that exploit this kind of access
wes_get_run_status. 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_get_run_status: 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_get_run_status 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_get_run_status 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_get_run_status. 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_get_run_status 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 →