Check audit log retention and monitoring configuration
AI agents call check_audit_log_settings to retrieve information from Google Workspace Compliance Audit Tool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and assesses audit log settings and retention policies—a read-only operation that queries existing configuration. While it doesn't modify data, the medium severity reflects that audit log configuration details could inform an attacker about detection capabilities or blind spots in logging coverage, making this information valuable for adversarial planning.
From the tool's definition Tool name 'check_audit_log_settings' and description 'Check audit log retention and monitoring configuration' indicate querying/retrieving configuration data without modifying it.
Attacks that exploit this kind of access
Check audit log retention and monitoring configuration. It is categorised as a Read tool in the Google Workspace Compliance Audit Tool MCP Server, which means it retrieves data without modifying state.
Register the Google Workspace Compliance Audit Tool MCP server in PolicyLayer and add a rule for check_audit_log_settings: 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 Google Workspace Compliance Audit Tool. Nothing to install.
check_audit_log_settings 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 check_audit_log_settings 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 check_audit_log_settings. 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.
check_audit_log_settings is provided by the Google Workspace Compliance Audit Tool MCP server (sean-m-sweeney/googleworkspaceaudit). 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 →