gets the HTML source code of the current page
AI agents call get_page_source to retrieve information from MCP Selenium Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data (HTML source code) from the current browser page. It performs no modifications, deletions, code execution, or external operations. The action is purely observational and read-only, consistent with the Read category. Severity is low because exposure of this tool allows information gathering about page structure but does not enable mutation or execution of arbitrary operations.
From the tool's definition Tool name 'get_page_source' and description 'gets the HTML source code of the current page' indicate retrieval of page content without modification or side effects.
Attacks that exploit this kind of access
gets the HTML source code of the current page. It is categorised as a Read tool in the MCP Selenium Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Selenium Server MCP server in PolicyLayer and add a rule for get_page_source: 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 MCP Selenium Server. Nothing to install.
get_page_source 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 get_page_source 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 get_page_source. 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.
get_page_source is provided by the MCP Selenium Server MCP server (sapangupta63/mcp-selenium-extended). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →