check_soundboard_playback

SERVERGuildControl MCP SOURCEguildctl

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/app-lasers-guildcontrol-discord/check-soundboard-playback.md

WHAT IT DOES

What check_soundboard_playback does on GuildControl MCP

AI agents call check_soundboard_playback to retrieve information from GuildControl MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why check_soundboard_playback is rated Low

Tool audits soundboard permissions and capabilities without modifying state or triggering playback.

From the tool's definition Check whether bot can play sound; verification without action.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_soundboard_playback 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 check_soundboard_playback, this is the rule to start with:

check_soundboard_playback Allowed

check_soundboard_playback is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_soundboard_playback": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect GuildControl MCP, apply this rule, and every check_soundboard_playback call is checked against it from then on.

FAQ

Questions about check_soundboard_playback

What does the check_soundboard_playback tool do? +

Check whether the verified bot can play one exact default or custom sound in one exact allowlisted ordinary voice channel. Fresh evidence must prove channel type and scope, complete overwrites and roles, VIEW_CHANNEL, CONNECT, SPEAK, USE_SOUNDBOARD, conditional USE_EXTERNAL_SOUNDS, the exact available sound, and the bot. It is categorised as a Read tool in the GuildControl MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_soundboard_playback? +

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

check_soundboard_playback is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_soundboard_playback? +

Yes. Add a rate_limit block to the check_soundboard_playback 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 check_soundboard_playback completely? +

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

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

KEEP EXPLORING

More on GuildControl, and thousands of servers like it.

This server

All 258 GuildControl tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →