AI agents call gemini_check_login to retrieve information from Gemini Skill without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the authentication state of a web page, returning information about whether a user is logged in. It is a pure read operation with no side effects—it does not create, modify, delete, or execute any operations. The potential misuse impact is minimal since knowing login status does not directly compromise security or functionality.
From the tool's definition Tool name 'gemini_check_login' and description '检查当前 Gemini 页面是否已登录 Google 账号' (Check if the current Gemini page is logged into a Google account) indicate a status query operation that retrieves login state without modifying any data or triggering external…
Documented attack patterns abuse exactly the kind of access gemini_check_login gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Gemini Skill, and nothing reaches the server without passing your rules. This is the rule we recommend for gemini_check_login:
{
"version": "1",
"default": "deny",
"tools": {
"gemini_check_login": {}
}
}gemini_check_login is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
检查当前 Gemini 页面是否已登录 Google 账号. It is categorised as a Read tool in the Gemini Skill MCP Server, which means it retrieves data without modifying state.
Register the Gemini Skill MCP server in PolicyLayer and add a rule for gemini_check_login: 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 Gemini Skill. Nothing to install.
gemini_check_login 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 gemini_check_login 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 gemini_check_login. 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.
gemini_check_login is provided by the Gemini Skill MCP server (wjz-p/gemini-skill). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 Gemini Skill tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
21 Gemini Skill tools catalogued and risk-classified — across an index of 42,500+ MCP servers.