Check for email forwarding rules to external addresses
AI agents call check_email_forwarding 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 audits existing email forwarding configurations to assess security/compliance posture. It retrieves and analyzes policy settings but does not create, modify, or delete forwarding rules. The blast radius of misuse is limited to information disclosure about current forwarding policies, which is low risk in a compliance audit context.
From the tool's definition Tool name 'check_' prefix and description 'Check for email forwarding rules' indicates query/audit operation.
Attacks that exploit this kind of access
Check for email forwarding rules to external addresses. 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_email_forwarding: 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_email_forwarding 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_email_forwarding 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_email_forwarding. 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_email_forwarding 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 →