AI agents call list_stickers 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 returns information about stickers without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with minimal security impact.
From the tool's definition Tool name 'list_stickers' and description 'List all custom stickers in a server' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all custom stickers in a server. 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 list_stickers: 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.
list_stickers 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 list_stickers 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 list_stickers. 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.
list_stickers is provided by the Discord MCP server (scarecr0w12/discord-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →