audit_guild_webhooks

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/audit-guild-webhooks.md

WHAT IT DOES

What audit_guild_webhooks does on GuildControl MCP

AI agents call audit_guild_webhooks 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 audit_guild_webhooks is rated Low

Tool audits and retrieves webhook metadata without mutation, credential exposure, or side effects.

From the tool's definition audit the complete Discord webhook inventory, returns exact IDs, omitting credentials, execution URLs, persists nothing

Attacks that exploit this kind of access

RECOMMENDED RULE

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

audit_guild_webhooks Allowed

audit_guild_webhooks 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": {
    "audit_guild_webhooks": {}
  }
}

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 audit_guild_webhooks call is checked against it from then on.

FAQ

Questions about audit_guild_webhooks

What does the audit_guild_webhooks tool do? +

Audit the complete Discord webhook inventory for one separately allowlisted guild with complete guild-level MANAGE_WEBHOOKS evidence. Returns exact IDs, transient untrusted webhook names, normalized types and application ownership, exposure aggregates, and fixed findings while omitting credentials, execution URLs, avatars, creator profiles and usernames, source objects, guild and channel names, channel topics, raw payloads, and unknown values. Persists nothing and grants no channel or mutation authority. 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 audit_guild_webhooks? +

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

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

Can I rate-limit audit_guild_webhooks? +

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

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

audit_guild_webhooks 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 →