moltbook_dm_messages
AI agents call moltbook_dm_messages to retrieve information from Moltbook MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the tool name and pattern of sibling tools, this appears to be a query/retrieval function for reading direct messages. While the empty description lowers confidence, the naming convention strongly suggests a read operation. No evidence of data modification, deletion, execution, or financial impact.
From the tool's definition Tool name 'moltbook_dm_messages' suggests retrieval of direct messages. No description provided, but the 'dm_' prefix and sibling tools like 'moltbook_dm_check', 'moltbook_dm_conversation', and 'moltbook_dm_conversations' are all read-oriented retrieval…
Attacks that exploit this kind of access
moltbook_dm_messages. It is categorised as a Read tool in the Moltbook MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Moltbook MCP Server MCP server in PolicyLayer and add a rule for moltbook_dm_messages: 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 Moltbook MCP Server. Nothing to install.
moltbook_dm_messages 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 moltbook_dm_messages 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 moltbook_dm_messages. 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.
moltbook_dm_messages is provided by the Moltbook MCP Server MCP server (thebenlamm/moltbook-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 →