deleteDirectMessagesEvents
Delete a specific direct message event permanently.
This record as markdown: /tools/xdevplatform-xmcp/deletedirectmessagesevents.md
What deleteDirectMessagesEvents does on Xdevplatform/xmcp
AI agents call deleteDirectMessagesEvents to permanently remove resources in Xdevplatform/xmcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why deleteDirectMessagesEvents is rated Critical
This tool permanently deletes direct message events, which cannot be undone. Permanent deletion of user communication data represents a destructive action with high blast radius if misused by an AI agent, as it could result in loss of important messages and inability to recover them. This is more severe than Write (which is reversible) and clearly destructive in nature.
From the tool's definition Tool name contains 'delete' and description states 'Delete a specific direct message event permanently.' The use of 'permanently' and 'delete' indicates irreversible data removal.
Attacks that exploit this kind of access
The rule that runs deleteDirectMessagesEvents safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Xdevplatform/xmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For deleteDirectMessagesEvents, this is the rule to start with:
deleteDirectMessagesEvents is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Xdevplatform/xmcp, apply this rule, and every deleteDirectMessagesEvents call is checked against it from then on.
Questions about deleteDirectMessagesEvents
Delete a specific direct message event permanently. It is categorised as a Destructive tool in the Xdevplatform/xmcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Xdevplatform/x MCP server in PolicyLayer and add a rule for deleteDirectMessagesEvents: 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.
deleteDirectMessagesEvents is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the deleteDirectMessagesEvents 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 deleteDirectMessagesEvents. 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.
deleteDirectMessagesEvents 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.
More on Xdevplatform/x, and thousands of servers like it.
Across the catalogue