audit_role_deletion

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-role-deletion.md

WHAT IT DOES

What audit_role_deletion does on GuildControl MCP

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

Tool retrieves and analyzes Discord role data for audit purposes without modifying, deleting, or executing any actions.

From the tool's definition Audit whether one exact role is ready for retirement without writing or persisting Discord data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

audit_role_deletion Allowed

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

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

FAQ

Questions about audit_role_deletion

What does the audit_role_deletion tool do? +

Audit whether one exact separately allowlisted Discord role is ready for retirement without writing or persisting Discord data. Requires a complete unobfuscated Gateway layout plus exact aggregate holders, hierarchy, permissions, channel overwrites, invite grants, emoji restrictions, onboarding options, AutoMod exemptions, integration ownership, and this-application command-permission inventories. Reports known platform blind spots explicitly. 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_role_deletion? +

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

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

Can I rate-limit audit_role_deletion? +

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

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

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