deleteDirectMessagesEvents

Delete a specific direct message event permanently.

Server Xdevplatform/xmcp xdevplatform/xmcp
Category Destructive
Risk class Critical
Parameters 00 required

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 needs a policy

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.

Questions about deleteDirectMessagesEvents

What does the deleteDirectMessagesEvents tool do? +

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.

How do I enforce a policy on deleteDirectMessagesEvents? +

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.

What risk level is deleteDirectMessagesEvents? +

deleteDirectMessagesEvents is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit deleteDirectMessagesEvents? +

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.

How do I block deleteDirectMessagesEvents completely? +

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.

What MCP server provides deleteDirectMessagesEvents? +

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.

// THE FULL RECORD

deleteDirectMessagesEvents 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.