cluster_cells

THE RISK

High Risk

Why cluster_cells needs a policy

This tool runs computational algorithms (Leiden/Louvain community detection, UMAP dimensionality reduction) on input data. It executes analytical processing pipelines rather than simply reading stored data or writing to a database. The results depend on the input dataset and algorithm parameters, classifying it as Execute.

From the tool's definition Cluster cells in a preprocessed single-cell dataset using Leiden or Louvain community detection. Returns cluster assignments and UMAP coordinates.

Documented attack patterns abuse exactly the kind of access cluster_cells gives an agent:

POLICY

How to control cluster_cells

PolicyLayer is an MCP gateway — it sits between your AI agents and MedSci Agent, and nothing reaches the server without passing your rules. This is the rule we recommend for cluster_cells:

policy.json

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

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

Create a free account and register MedSci Agent — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MedSci Agent tools

Destructive sandbox_teardown Stop or remove a Docker sandbox. By default only stops; set remove to true to also delete. Execute differential_expression Run differential expression analysis between cell groups. Identifies genes that are signif Execute sandbox_run_job Execute a command in an existing Docker sandbox and capture stdout, stderr, exit code, dur Execute preprocess_omics Preprocess a single-cell RNA-seq dataset: filter cells/genes, normalize, log-transform, an Execute sandbox_prepare Create or verify an isolated Docker sandbox for the workspace. Optionally apply a containe Read parse_fasta Parse a FASTA file and return sequence metadata: IDs, names, descriptions, lengths, and se Read acquire_documents Acquire policy-compliant scientific document text from DOI/PMID/PMCID/URL targets with pro Read analyze_medical_image Analyze a medical image (X-ray, CT, pathology slide, dermatology photo) using MedGemma

All 28 MedSci Agent tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in MedSci Agent → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about cluster_cells

What does the cluster_cells tool do? +

Cluster cells in a preprocessed single-cell dataset using Leiden or Louvain community detection. Returns cluster assignments and UMAP coordinates. It is categorised as a Execute tool in the MedSci Agent MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on cluster_cells? +

Register the MedSci Agent MCP server in PolicyLayer and add a rule for cluster_cells: 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 MedSci Agent. Nothing to install.

What risk level is cluster_cells? +

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

Can I rate-limit cluster_cells? +

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

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

cluster_cells is provided by the MedSci Agent MCP server (omar-a-hassan/medsci-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MedSci Agent tool call.

Start from MedSci Agent, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →