update_run_status · NGS360 MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_run_status does on NGS360 MCP Server

AI agents use update_run_status to create or update resources in NGS360 MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your NGS360 MCP Server environment.

WHY IT NEEDS A POLICY

Why update_run_status needs a policy

The tool modifies existing data (run status) but does not delete data irreversibly, does not execute arbitrary code, and does not involve financial transactions. Status updates are typically reversible (a run status can be changed from 'processing' to 'completed', 'failed', 'paused', etc.). This fits the Write category.

From the tool's definition Tool name 'update_run_status' and description 'Update the status of a sequencing run' indicate modification of run state data. This is a reversible change to run metadata/status in the NGS360 bioinformatics platform.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_run_status Rate-limited

update_run_status stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_run_status": {
      "limits": [
        {
          "counter": "update_run_status_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 update_run_status

What does the update_run_status tool do? +

Update the status of a sequencing run. It is categorised as a Write tool in the NGS360 MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_run_status? +

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

What risk level is update_run_status? +

update_run_status is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_run_status? +

Yes. Add a rate_limit block to the update_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.

How do I block update_run_status completely? +

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

What MCP server provides update_run_status? +

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