New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_direct_message

Read one exact Discord DM message from a caller-known one-to-one channel for one separately configured ordinary user. Re-verifies pinned connector identity, exact channel participants, recipient policy, message boundary, and author identity. Returns plain text or a supported callback-free static ...

SERVERGuildControl MCP SOURCEguildctl
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/app-lasers-guildcontrol-discord/get-direct-message.md

What get_direct_message does on GuildControl MCP

AI agents call get_direct_message to retrieve information from GuildControl MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_direct_message is rated Low

Retrieves DM message data with multiple safety controls but accesses personal communication content with privacy sensitivity.

From the tool's definition Read one exact Discord DM message; returns plain text; omits attachment URLs, raw payloads, persistence.

Questions about get_direct_message

What does the get_direct_message tool do? +

Read one exact Discord DM message from a caller-known one-to-one channel for one separately configured ordinary user. Re-verifies pinned connector identity, exact channel participants, recipient policy, message boundary, and author identity. Returns plain text or a supported callback-free static Components V2 layout transiently with deterministic preview, untrusted link destinations, presentation classification, and bounded aggregate counts while omitting generated and custom-ID component actions, profiles, avatars, attachment URLs, raw payloads, discovery, and persistence. It is categorised as a Read tool in the GuildControl MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_direct_message? +

Register the GuildControl MCP server in PolicyLayer and add a rule for get_direct_message: 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 GuildControl MCP. Nothing to install.

What risk level is get_direct_message? +

get_direct_message is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_direct_message? +

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

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

get_direct_message is provided by the GuildControl MCP server (guildctl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on GuildControl, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of GuildControl's. Pull the full record:

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.