AI agents call get_audit_logs to retrieve information from Discord without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a Read operation that queries existing audit log data. However, audit logs are sensitive information that could reveal server administration actions, user behavior patterns, and security events. While retrieval alone poses no direct destructive risk, the sensitivity of audit log data (which typically includes admin actions, bans, kicks, deletions, etc.) elevates severity to medium rather than low.
From the tool's definition Tool name is 'get_audit_logs' with description 'Get audit logs from a server' — it retrieves audit log data with no modification or side effects.
Attacks that exploit this kind of access
Get audit logs from a server. It is categorised as a Read tool in the Discord MCP Server, which means it retrieves data without modifying state.
Register the Discord MCP server in PolicyLayer and add a rule for get_audit_logs: 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.
get_audit_logs is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_audit_logs 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.
Set action: deny in the PolicyLayer policy for get_audit_logs. 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.
get_audit_logs is provided by the Discord MCP server (scarecr0w12/discord-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →