Get the HTML content of the current page.
AI agents call Get-Page-HTML to retrieve information from MCP GitHub Login Automation Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
While the tool itself performs a read-only operation (retrieving HTML), the context of GitHub login automation and credential management means the retrieved HTML may contain sensitive authentication data. This elevates it from 'low' to 'medium' severity due to potential exposure of session tokens or credentials, though it remains in the Read category since the tool itself performs no writes, deletes, or executions.
From the tool's definition Tool name 'Get-Page-HTML' and description 'Get the HTML content of the current page' indicate data retrieval with no modification.
Attacks that exploit this kind of access
Get the HTML content of the current page. It is categorised as a Read tool in the MCP GitHub Login Automation Server MCP Server, which means it retrieves data without modifying state.
Register the MCP GitHub Login Automation Server MCP server in PolicyLayer and add a rule for Get-Page-HTML: 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 GitHub Login Automation Server. Nothing to install.
Get-Page-HTML 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-HTML 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-HTML. 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-HTML is provided by the MCP GitHub Login Automation Server MCP server (nikhil-kandekar/mcp-server-demo). 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 →