Remove a member from a thread
AI agents call remove_thread_member to permanently remove resources in Discord — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a thread member revokes their access/membership from the thread. While the user could theoretically be re-added, the removal action itself is a deletion of membership state with no built-in undo, making it Destructive. Severity is medium because it affects a single user's access to a single thread, not server-wide data.
From the tool's definition "Remove a member from a thread" — the action of removing a member is irreversible in the sense that the membership is deleted/revoked without an undo mechanism.
Attacks that exploit this kind of access
Remove a member from a thread. It is categorised as a Destructive tool in the Discord MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Discord MCP server in PolicyLayer and add a rule for remove_thread_member: 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.
remove_thread_member is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_thread_member 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 remove_thread_member. 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.
remove_thread_member 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 →