Upload a new custom sticker to the server from a file URL.
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 and uploads a new sticker resource to the Discord server. While it modifies server state, it is reversible (stickers can be deleted) and has a limited blast radius—uploading stickers does not directly impact user access, financial systems, or critical infrastructure.
From the tool's definition Tool name: 'create_sticker'; description: 'Upload a new custom sticker to the server from a file URL.' The verb 'upload' and action of creating a new server resource indicates a Write operation that modifies server state by adding content.
Documented attack patterns abuse exactly the kind of access create_sticker 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 create_sticker:
{
"version": "1",
"default": "deny",
"tools": {
"create_sticker": {
"limits": [
{
"counter": "create_sticker_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_sticker stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Upload a new custom sticker to the server from a file URL. 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 (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.