execute_member_moderation
Execute one exact reviewed Discord member moderation plan after host write approval, signed interactive approval, a final fresh evidence match, durable exact-member coordination, one-shot receipt reservation, and pending content-free activity. Dispatches once without retry and requires exact fres...
This record as markdown: /tools/app-lasers-guildcontrol-discord/execute-member-moderation.md
What execute_member_moderation does on GuildControl MCP
AI agents invoke execute_member_moderation to trigger actions in GuildControl MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why execute_member_moderation is rated High
Executes moderation actions on Discord members with irreversible effects despite safeguards; classified as Execute rather than Destructive due to reversibility and approval mechanisms.
From the tool's definition Execute moderation plan, dispatches once without retry, requires approval
Attacks that exploit this kind of access
The rule that runs execute_member_moderation safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GuildControl MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For execute_member_moderation, this is the rule to start with:
execute_member_moderation stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GuildControl MCP, apply this rule, and every execute_member_moderation call is checked against it from then on.
Questions about execute_member_moderation
Execute one exact reviewed Discord member moderation plan after host write approval, signed interactive approval, a final fresh evidence match, durable exact-member coordination, one-shot receipt reservation, and pending content-free activity. Dispatches once without retry and requires exact fresh readback. It is categorised as a Execute tool in the GuildControl MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the GuildControl MCP server in PolicyLayer and add a rule for execute_member_moderation: 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 GuildControl MCP. Nothing to install.
execute_member_moderation is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the execute_member_moderation 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 execute_member_moderation. 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.
execute_member_moderation is provided by the GuildControl MCP server (guildctl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GuildControl, and thousands of servers like it.
Across the catalogue