wes_run_workflow · NGS360 MCP Server MCP: Risk & Policy

WHAT IT DOES

What wes_run_workflow does on NGS360 MCP Server

AI agents invoke wes_run_workflow to trigger actions in NGS360 MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why wes_run_workflow needs a policy

This tool executes workflows on a bioinformatics platform, which constitutes triggering external operations whose effects depend on arguments (workflow configuration, input data). The blast radius is high: misconfigured or malicious workflow execution could consume significant computational resources, produce incorrect results, or expose sensitive genomic data.

From the tool's definition Tool name 'wes_run_workflow' indicates execution of bioinformatics workflows. Context shows NGS360 is a sequencing/bioinformatics platform managing 'sequencing runs, projects, workflows' with sibling tools that create and manage pipelines and projects.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wes_run_workflow Rate-limited

wes_run_workflow stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wes_run_workflow": {
      "limits": [
        {
          "counter": "wes_run_workflow_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches NGS360 MCP Server, so you can run agents against it safely.

FAQ

Questions about wes_run_workflow

What does the wes_run_workflow tool do? +

wes_run_workflow. It is categorised as a Execute tool in the NGS360 MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on wes_run_workflow? +

Register the NGS360 MCP Server MCP server in PolicyLayer and add a rule for wes_run_workflow: 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.

What risk level is wes_run_workflow? +

wes_run_workflow is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit wes_run_workflow? +

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

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

wes_run_workflow 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.