// SCAN REPORT

decoupler-MCP

3 tools. 1 can modify or destroy data without limits.

1 write tool that can modify data. Rate limits recommended.

Last updated: 29 Jun 2026

1 can modify or destroy data

2 read-only

3 tools total

Community server · catalogue entry verified 29/06/2026

How to control decoupler-MCP ↓

TOOL MAP

What decoupler-MCP exposes to your agents

Read (2) Write / Execute (1) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous decoupler-MCP tools

Execute · Medium tf_activity This tool executes a bioinformatics computation (TF activity inference via decoupleR) against loaded datasets.

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

POLICY

How to control decoupler-MCP

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

Cap read operations

{
  "pathway_activity": {
    "limits": [
      {
        "counter": "pathway_activity_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 decoupler-MCP — 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 DECOUPLER-MCP →

Instant setup, no code required.

FULL CATALOGUE

All 3 decoupler-MCP tools

EXECUTE 1 tools

Execute tf_activity Transcription factor activity inference

READ 2 tools

Read pathway_activity Pathway activity inference Read retrieve_knowledge search function and parameters that can be used to solve the user's tasks or questions

FAQ

Questions about decoupler-MCP

Is the decoupler- MCP server safe to use without restrictions? +

The decoupler-MCP server is primarily read-only with 2 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the decoupler- MCP server expose? +

3 tools across 1 categories: Read. 2 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on decoupler-MCP? +

Register the decoupler- 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 decoupler-MCP tool call.

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

ENFORCE POLICY ON DECOUPLER-MCP →

Instant setup, no code required.

3 decoupler-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.