Retrieve message history for a topic or peer
AI agents call get_message_history 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 retrieves historical data without side effects. It queries existing message records from a peer-to-peer network or topic, comparable to a log retrieval or query operation. There is no creation, modification, deletion, or execution of commands. The context (DeFi/libp2p) does not change the nature of a retrieval operation.
From the tool's definition Tool name is 'get_message_history' and description states 'Retrieve message history for a topic or peer' — both indicate a read-only query operation with no modification, deletion, or execution of external code.
Attacks that exploit this kind of access
Retrieve message history for a topic or peer. 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 get_message_history: 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.
get_message_history 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 get_message_history 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 get_message_history. 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.
get_message_history 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 →