// SCAN REPORT

NGS360 MCP Server

82 tools. 36 can modify or destroy data without limits.

10 destructive tools with no built-in limits. Policy required.

Last updated: 2 Jul 2026

36 can modify or destroy data

46 read-only

82 tools total

Community server · catalogue entry verified 02/07/2026

How to control NGS360 MCP Server ↓

TOOL MAP

What NGS360 MCP Server exposes to your agents

Read (46) Write / Execute (26) Destructive / Financial (10)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous NGS360 MCP Server tools

Destructive · Critical delete_file This tool irreversibly removes data from the system. Destructive · High delete_sample_from_project This tool permanently deletes sample data from a project with no recovery mechanism. Destructive · High clear_samples_for_run This tool irreversibly removes sample associations from a sequencing run, deleting relational data with no undo mechanism. Destructive · High delete_qcrecord This tool permanently removes QC (quality control) records and all associated data from the NGS360 bioinformatics platform.

36 of NGS360 MCP Server's 82 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control NGS360 MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and NGS360 MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "clear_samples_for_run": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "add_sample_to_project": {
    "limits": [
      {
        "counter": "add_sample_to_project_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "browse_s3": {
    "limits": [
      {
        "counter": "browse_s3_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register NGS360 MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON NGS360 →

Instant setup, no code required.

FULL CATALOGUE

All 82 NGS360 MCP Server tools

DESTRUCTIVE 10 tools

Destructive clear_samples_for_run Remove all sample associations and cleanup for a run (re-demux scenario). Destructive delete_file Delete a file record and all associated data (superuser only, irreversible). Destructive delete_qcrecord Delete a QC record and all associated data (irreversible). Destructive delete_sample_from_project Delete a sample from a project (superuser only, irreversible). Destructive delete_vendor Delete a vendor. Destructive delete_workflow_alias Remove an alias from a workflow. Destructive delete_workflow_deployment Remove a platform deployment. Destructive remove_sample_from_run Remove a single sample association from a run. Destructive remove_workflow_from_pipeline Remove a workflow from a pipeline. Destructive wes_cancel_run Cancel a running workflow.

EXECUTE 5 tools

Execute create_workflow_deployment Deploy a workflow version on a specific platform. Execute submit_demux_job Submit a demultiplex workflow job. Execute submit_job submit_job Execute submit_pipeline_job submit_pipeline_job Execute wes_run_workflow wes_run_workflow

WRITE 21 tools

Write add_sample_to_project Add a sample to a project. Write add_workflow_to_pipeline Add a workflow to a pipeline. Write associate_sample_with_run Associate a sample with a sequencing run. Write create_file_record create_file_record Write create_pipeline Create a new pipeline (named collection of workflows). Write create_platform Create a new workflow execution platform. Write create_project Create a new project. Write create_qcrecord create_qcrecord Write create_run create_run Write create_vendor Create a new vendor. Write create_workflow Create a new workflow identity. Write create_workflow_version Create a new version for a workflow. Write ingest_vendor_data Ingest vendor data for a project. Write patch_project patch_project Write set_workflow_alias Set or update a workflow version alias (e.g., 'production'). Write update_file update_file Write update_job update_job Write update_project update_project Write update_run_status Update the status of a sequencing run. Write update_setting update_setting Write update_vendor Update a vendor's information.

READ 46 tools

Read browse_s3 Browse files and folders at an S3 URI. Read get_demux_workflow_config Get configuration for a specific demultiplex workflow. Read get_file Get file metadata by UUID. Read get_file_versions Get all versions of a file. Read get_job Get details of a specific batch job. Read get_job_log Get the full log output for a batch job. Read get_job_log_paginated Get paginated log output for a batch job. Read get_latest_manifest Get the latest manifest file path from an S3 bucket. Read get_pipeline Get details of a specific pipeline. Read get_platform Get a platform by name. Read get_project Get details of a specific project. Read get_project_samples get_project_samples Read get_qcrecord Get a specific QC record by UUID. Read get_run Get details of a specific sequencing run. Read get_run_metrics Get demultiplexing metrics for a sequencing run. Read get_run_samplesheet Get the sample sheet for a sequencing run. Read get_samples_for_run List sample associations for a sequencing run. Read get_setting Get a specific setting by key. Read get_settings_by_tag Get settings filtered by a tag key-value pair. Read get_vendor Get details of a specific vendor. Read get_workflow Get details of a specific workflow. Read get_workflow_version Get a specific workflow version. Read list_demux_workflows List available demultiplex workflows. Read list_files list_files Read list_jobs list_jobs Read list_pipelines List pipelines with pagination and sorting. Read list_platforms List all registered workflow execution platforms. Read list_projects List projects with pagination and sorting. Read list_runs List sequencing runs with pagination and sorting. Read list_vendors List vendors with pagination and sorting. Read list_workflow_aliases List aliases for a workflow. Read list_workflow_deployments list_workflow_deployments Read list_workflow_versions List all versions of a workflow. Read list_workflows List workflows with pagination and sorting. Read search Search across all indices (projects, runs, samples) using OpenSearch. Read search_projects Search projects by project_id or name. Read search_qcrecords search_qcrecords Read search_qcrecords_advanced search_qcrecords_advanced Read search_runs search_runs Read validate_manifest validate_manifest Read wes_get_run_log Get detailed information about a workflow run. Read wes_get_run_status wes_get_run_status Read wes_get_service_info Get information about the WES service. Read wes_get_task Get details of a specific task within a workflow run. Read wes_list_runs List workflow runs from the WES service. Read wes_list_tasks wes_list_tasks

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about NGS360 MCP Server

Can an AI agent delete data through the NGS360 MCP Server MCP server? +

Yes. The NGS360 MCP Server server exposes 10 destructive tools including clear_samples_for_run, delete_file, delete_qcrecord. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through NGS360 MCP Server? +

The NGS360 MCP Server server has 21 write tools including add_sample_to_project, add_workflow_to_pipeline, associate_sample_with_run. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach NGS360 MCP Server.

How many tools does the NGS360 MCP Server MCP server expose? +

82 tools across 4 categories: Destructive, Execute, Read, Write. 46 are read-only. 36 can modify, create, or delete data.

How do I enforce a policy on NGS360 MCP Server? +

Register the NGS360 MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every NGS360 MCP Server tool call.

Deterministic rules across all 82 NGS360 MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON NGS360 →

Instant setup, no code required.

82 NGS360 MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// WHERE THIS COMES FROM

These policies come from NGS360 MCP Server's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →