Edit an existing application (slash) command. You can update its name and/or description.
AI agents use edit_command 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.
The tool modifies existing Discord slash commands by updating their name and/or description. This is a reversible write operation that changes application state without deleting data or executing arbitrary code. Severity is medium because misconfigured commands could impact server usability and user experience, but the operation is not destructive or financial.
From the tool's definition Tool description states 'Edit an existing application (slash) command. You can update its name and/or description.' — these are modify operations (update).
Documented attack patterns abuse exactly the kind of access edit_command 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 edit_command:
{
"version": "1",
"default": "deny",
"tools": {
"edit_command": {
"limits": [
{
"counter": "edit_command_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} edit_command 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.
Edit an existing application (slash) command. You can update its name and/or description. 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 edit_command: 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.
edit_command 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 edit_command 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 edit_command. 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.
edit_command 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.