Get all pinned messages in a thread.
AI agents call get_thread_pinned_messages to retrieve information from Discord without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing pinned messages from a Discord thread. It performs no mutations, deletions, or external operations. The action is purely informational and has no blast radius if misused by an agent—at worst, it exposes data already visible to users with read permissions in that thread.
From the tool's definition Tool name 'get_thread_pinned_messages' and description 'Get all pinned messages in a thread' indicate a read-only retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_thread_pinned_messages gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Discord, and nothing reaches the server without passing your rules. This is the rule we recommend for get_thread_pinned_messages:
{
"version": "1",
"default": "deny",
"tools": {
"get_thread_pinned_messages": {}
}
}get_thread_pinned_messages is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get all pinned messages in a thread. It is categorised as a Read tool in the Discord MCP Server, which means it retrieves data without modifying state.
Register the Discord MCP server in PolicyLayer and add a rule for get_thread_pinned_messages: 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 Discord. Nothing to install.
get_thread_pinned_messages 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_thread_pinned_messages 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_thread_pinned_messages. 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_thread_pinned_messages is provided by the Discord MCP server (hardheadhackerhead/discord-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Discord, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
139 Discord tools catalogued and risk-classified — across an index of 43,000+ MCP servers.