check_email_authentication

Check SPF, DKIM, and DMARC email authentication status

Server Google Workspace Compliance Audit Tool sean-m-sweeney/googleworkspaceaudit
Category Read
Risk class Low
Parameters 00 required

What check_email_authentication does on Google Workspace Compliance Audit Tool

AI agents call check_email_authentication 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.

Why check_email_authentication needs a policy

This tool retrieves and inspects email authentication configurations (SPF, DKIM, DMARC records/settings) to assess their compliance status. It performs no modifications to data, executes no commands, and causes no side effects. It is a read-only audit function typical of compliance assessment tools.

From the tool's definition Tool name 'check_email_authentication' and description 'Check SPF, DKIM, and DMARC email authentication status' indicate a query/audit operation that retrieves and assesses the configuration status of email authentication protocols.

Questions about check_email_authentication

What does the check_email_authentication tool do? +

Check SPF, DKIM, and DMARC email authentication status. It is categorised as a Read tool in the Google Workspace Compliance Audit Tool MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_email_authentication? +

Register the Google Workspace Compliance Audit Tool MCP server in PolicyLayer and add a rule for check_email_authentication: 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.

What risk level is check_email_authentication? +

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

Can I rate-limit check_email_authentication? +

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

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

check_email_authentication 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.