AI agents use create_sticker to create or update resources in Discord — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Discord environment.
This tool creates a new sticker asset in a Discord server, which is a Write operation—data is created and stored but can be reversed (the sticker can be deleted). The severity is medium because misuse could result in spam stickers or resource waste, but the impact is limited to aesthetic/organizational aspects of the server without affecting core data integrity, financial commitments, or destructive outcomes.
From the tool's definition Tool name 'create_sticker' and description 'Create a custom sticker in a server' indicate creation of new server assets. Creation is a reversible modification operation.
Attacks that exploit this kind of access
Create a custom sticker in a server. It is categorised as a Write tool in the Discord MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Discord MCP server in PolicyLayer and add a rule for create_sticker: 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.
create_sticker is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_sticker 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 create_sticker. 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.
create_sticker 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 →