// SCAN REPORT

PullNexus

11 tools. 4 can modify or destroy data without limits.

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

Last updated: 12 Jun 2026

4 can modify or destroy data

7 read-only

11 tools total

Community server · catalogue entry verified 12/06/2026

How to control PullNexus ↓

TOOL MAP

What PullNexus exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous PullNexus tools

Execute · High pullnexus_install An 'install' operation typically downloads and executes code or artifacts on the local system, which constitutes an Execute-level action.

4 of PullNexus's 11 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control PullNexus

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

Cap read operations

{
  "my_tool": {
    "limits": [
      {
        "counter": "my_tool_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 PullNexus — 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 PULLNEXUS →

Free to start. No card required.

FULL CATALOGUE

All 11 PullNexus tools

EXECUTE 1 tools

Execute pullnexus_install pullnexus_install

READ 7 tools

Read my_tool my_tool Read pullnexus_hints_needed pullnexus_hints_needed Read pullnexus_info Get full metadata and README for a PullNexus resource. Read pullnexus_model_context pullnexus_model_context Read pullnexus_recommend pullnexus_recommend Read pullnexus_search pullnexus_search Read pullnexus_types List all resource types in the PullNexus registry with counts.

OTHER 3 tools

Other async_tool async_tool Other pullnexus_feedback pullnexus_feedback Other tool_with_context tool_with_context

FAQ

Questions about PullNexus

Is the PullNexus MCP server safe to use without restrictions? +

The PullNexus server is primarily read-only with 7 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 PullNexus MCP server expose? +

11 tools across 2 categories: Read, Write. 7 are read-only. 4 can modify, create, or delete data.

How do I enforce a policy on PullNexus? +

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

Deterministic rules across all 11 PullNexus tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON PULLNEXUS →

Free to start. No card required.

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