check_api_access

Check third-party API access and OAuth app permissions

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

What check_api_access does on Google Workspace Compliance Audit Tool

AI agents call check_api_access 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_api_access needs a policy

This tool retrieves and queries information about existing API access and OAuth permissions in a Google Workspace environment. It performs inspection and assessment without modifying configurations, executing code, or causing destructive effects. While the information retrieved could reveal sensitive security posture (elevating it beyond low severity), the tool itself is read-only.

From the tool's definition Tool name and description indicate it 'Check[s] third-party API access and OAuth app permissions' — a query/inspection operation with no modification or execution capabilities mentioned.

Questions about check_api_access

What does the check_api_access tool do? +

Check third-party API access and OAuth app permissions. 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_api_access? +

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

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

Can I rate-limit check_api_access? +

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

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

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

// THE FULL RECORD

check_api_access is one line of Google Workspace Compliance Audit Tool's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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.