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 ...
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.
Attacks that exploit this kind of access
The rule that runs get_direct_message safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GuildControl MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_direct_message, this is the rule to start with:
get_direct_message is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GuildControl MCP, apply this rule, and every get_direct_message call is checked against it from then on.
Questions about 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 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.
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.
get_direct_message is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
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.
This server
Across the catalogue