Send private message directly to a peer
AI agents use send_direct_message to create or update resources in JS-Peer x DeFi MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your JS-Peer x DeFi MCP Server environment.
This tool creates and transmits data (a private message) to another peer in a libp2p network. While it has no permanent destructive effect and doesn't execute code or move funds, it does modify the network state by introducing new messages.
From the tool's definition Tool name 'send_direct_message' and description 'Send private message directly to a peer' indicate message creation and transmission to another network participant.
Attacks that exploit this kind of access
Send private message directly to a peer. It is categorised as a Write tool in the JS-Peer x DeFi MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the JS-Peer x DeFi MCP Server MCP server in PolicyLayer and add a rule for send_direct_message: 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.
send_direct_message is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the send_direct_message 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 send_direct_message. 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.
send_direct_message 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 →