blockUsersDms

Block a user from sending direct messages to the authenticated user.

SERVERXdevplatform/xmcp SOURCExdevplatform/xmcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/xdevplatform-xmcp/blockusersdms.md

WHAT IT DOES

What blockUsersDms does on Xdevplatform/xmcp

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

RISK

Why blockUsersDms is rated Medium

This tool modifies a relationship/permission state by blocking a user from sending DMs. It is reversible (users can be unblocked), so it falls under Write rather than Destructive. Misuse could affect user communications and relationships.

From the tool's definition Block a user from sending direct messages to the authenticated user

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs blockUsersDms 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 blockUsersDms, this is the rule to start with:

blockUsersDms Rate-limited

blockUsersDms 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": {
    "blockUsersDms": {
      "limits": [
        {
          "counter": "blockusersdms_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Xdevplatform/xmcp, apply this rule, and every blockUsersDms call is checked against it from then on.

FAQ

Questions about blockUsersDms

What does the blockUsersDms tool do? +

Block a user from sending direct messages to the authenticated user. 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 blockUsersDms? +

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

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

Can I rate-limit blockUsersDms? +

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

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

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

KEEP EXPLORING

More on Xdevplatform/x, and thousands of servers like it.

This server

All 135 Xdevplatform/x tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →