// SCAN REPORT

Nekzus

19 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated:

0 can modify or destroy data
19 read-only
19 tools total
// TOOL MAP
Read (19) Write / Execute (0) Destructive / Financial (0)
// WHAT CAN GO WRONG
✕

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

One command. Full control.

Intercept sits between your agent and Nekzus. Every tool call checked against your policy before it executes — so your agent can do its job without breaking things.

npx -y @policylayer/intercept scan -- npx -y @nekzus/mcp-server
Scans every tool. Generates a policy. Starts enforcing.
Works with Claude Code · Cursor · Claude Desktop · Windsurf · any MCP client
// RECOMMENDED RULES
Cap read operations
npmAlternatives:
  rules:
    - rate_limit: 60/minute

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

// ALL 19 NEKZUS TOOLS
READ 19 tools
Read npmAlternatives Read npmChangelogAnalysis Read npmCompare Read npmDeprecated Read npmDeps Read npmLatest Read npmLicenseCompatibility Read npmMaintainers Read npmMaintenance Read npmPackageReadme Read npmQuality Read npmRepoStats Read npmScore Read npmSearch Read npmSize Read npmTrends Read npmTypes Read npmVersions Read npmVulnerabilities
// FAQ
Is the Nekzus MCP server safe to use without restrictions? +

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

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

How do I add Intercept to my Nekzus setup? +

One line change. Instead of running the Nekzus server directly, prefix it with Intercept: intercept -c io-github-nekzus-npm-sentinel-mcp.yaml -- npx -y @@nekzus/mcp-server. Download a pre-built policy from policylayer.com/policies/io-github-nekzus-npm-sentinel-mcp and adjust the limits to match your use case.

policylayer/intercept

Control every MCP tool call
your agent makes.

Set budgets, approvals, and hard limits across MCP servers.

npx -y @policylayer/intercept init
Protect your agent in 30 seconds. Scans your MCP config and generates enforcement policies for every server.
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.