Send a direct message in an existing DM conversation.
AI agents use createDirectMessagesByConversationId to create or update resources in Xdevplatform/xmcp — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Xdevplatform/xmcp environment.
The tool creates new message records in a direct messaging system. This is reversible (messages can typically be deleted) and has a defined, bounded scope (writes only to an existing conversation). It does not execute arbitrary code, delete data, or move funds. Severity is medium because misuse could send unwanted messages to users, but the blast radius is limited to messaging rather than system-wide impacts.
From the tool's definition Tool name contains 'create' and description states 'Send a direct message in an existing DM conversation' — this creates/writes new message data to an existing conversation.
Attacks that exploit this kind of access
Send a direct message in an existing DM conversation. It is categorised as a Write tool in the Xdevplatform/xmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Xdevplatform/x MCP server in PolicyLayer and add a rule for createDirectMessagesByConversationId: 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 Xdevplatform/xmcp. Nothing to install.
createDirectMessagesByConversationId 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 createDirectMessagesByConversationId 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 createDirectMessagesByConversationId. 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.
createDirectMessagesByConversationId is provided by the Xdevplatform/x MCP server (xdevplatform/xmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
createDirectMessagesByConversationId is one line of Xdevplatform/x'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 →