Get all active connections with metadata
AI agents call list_connections to retrieve information from JS-Peer x DeFi MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns metadata about existing peer-to-peer connections. It performs information retrieval only—no data is created, modified, deleted, or executed. The blast radius is minimal: an agent could learn the topology of connected peers, but cannot alter connections or trigger actions. While running on a DeFi/libp2p server, the tool itself is purely observational.
From the tool's definition Tool name 'list_connections' and description 'Get all active connections with metadata' indicate retrieval of connection state information without modification or side effects.
Attacks that exploit this kind of access
Get all active connections with metadata. It is categorised as a Read tool in the JS-Peer x DeFi MCP Server MCP Server, which means it retrieves data without modifying state.
Register the JS-Peer x DeFi MCP Server MCP server in PolicyLayer and add a rule for list_connections: 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.
list_connections is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_connections 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.
Set action: deny in the PolicyLayer policy for list_connections. 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.
list_connections 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →