New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

execute_message_forward

Forward one exact eligible Discord message snapshot after a fresh matching plan, signed interactive approval, unique one-shot operation-key reservation, durable exact-target coordination, pending content-free records, one non-retried create request with empty mentions and suppressed notifications...

SERVERGuildControl MCP SOURCEguildctl
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/app-lasers-guildcontrol-discord/execute-message-forward.md

What execute_message_forward does on GuildControl MCP

AI agents invoke execute_message_forward 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_message_forward is rated High

Forwards message content to new Discord locations with irreversible effects and no rollback capability.

From the tool's definition forward message snapshot, one-shot operation-key, no automatic rollback

Questions about execute_message_forward

What does the execute_message_forward tool do? +

Forward one exact eligible Discord message snapshot after a fresh matching plan, signed interactive approval, unique one-shot operation-key reservation, durable exact-target coordination, pending content-free records, one non-retried create request with empty mentions and suppressed notifications, strict response validation, and exact independent readback. The immutable snapshot exposes source content to target readers and the workflow has no automatic rollback. 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.

How do I enforce a policy on execute_message_forward? +

Register the GuildControl MCP server in PolicyLayer and add a rule for execute_message_forward: 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.

What risk level is execute_message_forward? +

execute_message_forward is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit execute_message_forward? +

Yes. Add a rate_limit block to the execute_message_forward 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.

How do I block execute_message_forward completely? +

Set action: deny in the PolicyLayer policy for execute_message_forward. 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.

What MCP server provides execute_message_forward? +

execute_message_forward 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of GuildControl's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.