Lock a channel by denying SendMessages for @everyone. Quick shortcut for permission management.
AI agents use lock_channel 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.
lock_channel modifies channel state by changing permissions (denying SendMessages), making it a Write operation. The severity is medium because it restricts functionality for all channel members but remains reversible—the lock can be undone by restoring permissions. It is not Destructive (no data deletion), Execute (no code execution), or Financial (no monetary impact).
From the tool's definition Tool description states it denies SendMessages permission for @everyone, which modifies channel permissions. This is a reversible permission change that affects message-sending capability but does not delete data or execute arbitrary code.
Documented attack patterns abuse exactly the kind of access lock_channel 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 lock_channel:
{
"version": "1",
"default": "deny",
"tools": {
"lock_channel": {
"limits": [
{
"counter": "lock_channel_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} lock_channel 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.
Lock a channel by denying SendMessages for @everyone. Quick shortcut for permission management. 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 lock_channel: 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.
lock_channel 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 lock_channel 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 lock_channel. 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.
lock_channel 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.