Read the Zendesk audit log (who changed what, when). Filter by source_type, actor_id, and time window. Read-only. Requires Zendesk Enterprise. Use this to verify a change landed or to detect config drift.
AI agents call zda_audit_logs to retrieve information from Zendesk Admin MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical audit log records for inspection and verification purposes with no side effects. It enables querying and listing past configuration changes, which is a classic Read operation. The low severity reflects minimal blast radius—viewing audit logs cannot harm system state or data integrity.
From the tool's definition Tool description explicitly states 'Read-only' and describes retrieving audit log data: 'who changed what, when' with filtering capabilities. No create, modify, delete, or execute operations are performed.
Attacks that exploit this kind of access
Read the Zendesk audit log (who changed what, when). Filter by source_type, actor_id, and time window. Read-only. Requires Zendesk Enterprise. Use this to verify a change landed or to detect config drift. It is categorised as a Read tool in the Zendesk Admin MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Zendesk Admin MCP Server MCP server in PolicyLayer and add a rule for zda_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 Zendesk Admin MCP Server. Nothing to install.
zda_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 zda_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 zda_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.
zda_audit_logs is provided by the Zendesk Admin MCP Server MCP server (sniebauer/zendesk-admin-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 →