get_widget

THE RISK

Low Risk

Why get_widget needs a policy

This tool retrieves configuration data about Discord server widget settings (enabled status and associated channel). It performs a read-only query with no capability to modify, delete, or execute actions. The blast radius if misused by an agent is minimal—an attacker gains knowledge of public widget configuration at most.

From the tool's definition Tool name 'get_widget' and description 'Get the server widget settings' indicate a retrieval operation with no modification or side effects.

Documented attack patterns abuse exactly the kind of access get_widget gives an agent:

POLICY

How to control get_widget

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 get_widget:

policy.json

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

get_widget is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Discord — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Discord tools

Destructive bulk_delete_messages Delete multiple messages from a channel at once (2-100 messages). Only works on messages l Destructive delete_automod_rule Delete an auto-moderation rule from the Discord server. Destructive delete_channel Delete a channel from the Discord server. Channel name is fuzzy-matched. Destructive delete_command Delete an application (slash) command. Destructive delete_emoji Remove a custom emoji from the server by name or ID. Destructive delete_event Delete a scheduled event from the Discord server. Destructive delete_forum_tag Remove a tag from a forum channel. Destructive delete_integration Remove an integration from the server by its ID.

All 139 Discord tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_widget

What does the get_widget tool do? +

Get the server widget settings including whether it is enabled and which channel it uses. It is categorised as a Read tool in the Discord MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_widget? +

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

What risk level is get_widget? +

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

Can I rate-limit get_widget? +

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

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

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

Enforce policy on every Discord tool call.

Start from Discord, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →