AI agents invoke gemini_reload_page to trigger actions in Gemini Skill. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a browser action (page reload) through Chrome DevTools Protocol, which is an external operation that affects the state of a running browser session. It doesn't merely read data, nor does it write, delete, or move money — it performs a browser-level action whose effect (resetting page state, potentially losing unsaved data) classifies it as Execute.
From the tool's definition 刷新 Gemini 页面（页面卡住或状态异常时使用） — triggers a browser page reload action via CDP
Documented attack patterns abuse exactly the kind of access gemini_reload_page 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_reload_page:
{
"version": "1",
"default": "deny",
"tools": {
"gemini_reload_page": {
"limits": [
{
"counter": "gemini_reload_page_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}gemini_reload_page stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
刷新 Gemini 页面（页面卡住或状态异常时使用）. It is categorised as a Execute tool in the Gemini Skill MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Gemini Skill MCP server in PolicyLayer and add a rule for gemini_reload_page: 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_reload_page is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the gemini_reload_page 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_reload_page. 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_reload_page 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.