verify_direct_message_change
Verify one exact caller-retained private-message change request against its token-keyed schema-v2 content-free operation receipt and receipt-bound exact Discord message or absence. Receipt and request matching plus current exact link-origin policy enforcement happen before Discord or local-file a...
This record as markdown: /tools/app-lasers-guildcontrol-discord/verify-direct-message-change.md
What verify_direct_message_change does on GuildControl MCP
AI agents call verify_direct_message_change 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 verify_direct_message_change is rated Low
Verifies and reads DM change metadata without fetching links, writing, or scanning channels; no side effects.
From the tool's definition verify, returns only lifecycle status, exact IDs, hashes, timestamps, match state
Attacks that exploit this kind of access
The rule that runs verify_direct_message_change 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 verify_direct_message_change, this is the rule to start with:
verify_direct_message_change 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 verify_direct_message_change call is checked against it from then on.
Questions about verify_direct_message_change
Verify one exact caller-retained private-message change request against its token-keyed schema-v2 content-free operation receipt and receipt-bound exact Discord message or absence. Receipt and request matching plus current exact link-origin policy enforcement happen before Discord or local-file access. Returns only lifecycle status, exact IDs, hashes, timestamps, and fresh match state; attachment recovery compares receipt-bound size and caller-retained metadata without reopening the local file or downloading Discord content. It never fetches links, writes, reserves, scans private channels, persists or returns message content, or trusts caller-supplied recovery identities. 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 verify_direct_message_change: 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.
verify_direct_message_change 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 verify_direct_message_change 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 verify_direct_message_change. 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.
verify_direct_message_change 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