google_profile_all

List all configured Google accounts with their email addresses, display names, and OAuth scope status. Use this first to discover which account aliases are available and verify they have the scopes needed for other tools.

Server Access scottpedia0/access
Category Read
Risk class Low
Parameters 00 required

What google_profile_all does on Access

AI agents call google_profile_all to retrieve information from Access without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why google_profile_all needs a policy

This tool retrieves metadata about configured Google accounts and their OAuth status. While it exposes sensitive information (email addresses, display names, OAuth scope details) that could aid in privilege escalation or account enumeration attacks, it performs no write, execute, or destructive operations.

From the tool's definition Tool description states 'List all configured Google accounts' — a query operation with no modification capability. The verb 'List' and the retrieval-only nature (discover, verify) confirms read-only access.

Risk signalsBulk/mass operation — affects multiple targets

Questions about google_profile_all

What does the google_profile_all tool do? +

List all configured Google accounts with their email addresses, display names, and OAuth scope status. Use this first to discover which account aliases are available and verify they have the scopes needed for other tools. It is categorised as a Read tool in the Access MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on google_profile_all? +

Register the Access MCP server in PolicyLayer and add a rule for google_profile_all: 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 Access. Nothing to install.

What risk level is google_profile_all? +

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

Can I rate-limit google_profile_all? +

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

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

google_profile_all is provided by the Access MCP server (scottpedia0/access). 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.