Navigate the current browser tab to a Photon documentation page by route or URL.
AI agents invoke photon_open_docs_page to trigger actions in Photon MCP Server. 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 performs a browser action (navigating the current browser tab), which is an Execute-category operation. It triggers an external operation (browser navigation) whose effects depend on the arguments provided. While the navigation target is documentation pages, the act of controlling the browser tab is an execution action, not merely reading data.
From the tool's definition Navigate the current browser tab to a Photon documentation page by route or URL
Documented attack patterns abuse exactly the kind of access photon_open_docs_page gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Photon MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for photon_open_docs_page:
{
"version": "1",
"default": "deny",
"tools": {
"photon_open_docs_page": {
"limits": [
{
"counter": "photon_open_docs_page_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} photon_open_docs_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.
Navigate the current browser tab to a Photon documentation page by route or URL. It is categorised as a Execute tool in the Photon MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Photon MCP Server MCP server in PolicyLayer and add a rule for photon_open_docs_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 Photon MCP Server. Nothing to install.
photon_open_docs_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 photon_open_docs_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 photon_open_docs_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.
photon_open_docs_page is provided by the Photon MCP Server MCP server (portel-dev/photon). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 Photon MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
6 Photon MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.