stop_libp2p_node · JS-Peer x DeFi MCP Server MCP

WHAT IT DOES

What stop_libp2p_node does on JS-Peer x DeFi MCP Server

AI agents invoke stop_libp2p_node to trigger actions in JS-Peer x DeFi MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why stop_libp2p_node needs a policy

The tool executes a command to shut down a libp2p network node. While 'gracefully shutdown' suggests a safe operation (reversible via restart), it triggers an external process with immediate side effects on network availability and operations. It is Execute (not Destructive) because the state can be recovered by restarting the node.

From the tool's definition Tool name: 'stop_libp2p_node'; description: 'Gracefully shutdown the libp2p node'. This performs an external system operation that terminates network infrastructure.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_libp2p_node Rate-limited

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

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches JS-Peer x DeFi MCP Server, so you can run agents against it safely.

FAQ

Questions about stop_libp2p_node

What does the stop_libp2p_node tool do? +

Gracefully shutdown the libp2p node. It is categorised as a Execute tool in the JS-Peer x DeFi MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on stop_libp2p_node? +

Register the JS-Peer x DeFi MCP Server MCP server in PolicyLayer and add a rule for stop_libp2p_node: 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 JS-Peer x DeFi MCP Server. Nothing to install.

What risk level is stop_libp2p_node? +

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

Can I rate-limit stop_libp2p_node? +

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

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

stop_libp2p_node is provided by the JS-Peer x DeFi MCP Server MCP server (nkovaturient/js-peer-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

stop_libp2p_node is one line of JS-Peer x DeFi MCP Server's registry record.

The record carries the whole server: 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 →