createDirectMessagesByParticipantId

WHAT IT DOES

What createDirectMessagesByParticipantId does on Xdevplatform/xmcp

AI agents use createDirectMessagesByParticipantId 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.

WHY IT NEEDS A POLICY

Why createDirectMessagesByParticipantId needs a policy

This tool creates and modifies data (direct message and conversation records) in a reversible manner. While sending unsolicited messages could constitute harassment or spam, the action itself is not destructive (messages can be deleted) and does not involve financial transactions or code execution.

From the tool's definition Tool description states 'Send a direct message to a specific user, creating a conversation if needed' — creates a new conversation object and writes message data to the system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

createDirectMessagesByParticipantId Rate-limited

createDirectMessagesByParticipantId stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "createDirectMessagesByParticipantId": {
      "limits": [
        {
          "counter": "createdirectmessagesbyparticipantid_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Xdevplatform/xmcp, so you can run agents against it safely.

FAQ

Questions about createDirectMessagesByParticipantId

What does the createDirectMessagesByParticipantId tool do? +

Send a direct message to a specific user, creating a conversation if needed. 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.

How do I enforce a policy on createDirectMessagesByParticipantId? +

Register the Xdevplatform/x MCP server in PolicyLayer and add a rule for createDirectMessagesByParticipantId: 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 createDirectMessagesByParticipantId? +

createDirectMessagesByParticipantId is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit createDirectMessagesByParticipantId? +

Yes. Add a rate_limit block to the createDirectMessagesByParticipantId 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 createDirectMessagesByParticipantId completely? +

Set action: deny in the PolicyLayer policy for createDirectMessagesByParticipantId. 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 createDirectMessagesByParticipantId? +

createDirectMessagesByParticipantId 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.