Find elements using an XPath expression and return their count.
AI agents call Browser-Find-By-XPath 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.
This tool only queries the DOM to locate elements matching an XPath expression and returns a count — a read-only operation with no side effects. However, it exists within a credential-management browser automation context, so misuse in combination with other tools could expose sensitive data, but the tool itself performs no writes or executions.
From the tool's definition Find elements using an XPath expression and return their count
Attacks that exploit this kind of access
Find elements using an XPath expression and return their count. 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 Browser-Find-By-XPath: 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.
Browser-Find-By-XPath 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 Browser-Find-By-XPath 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 Browser-Find-By-XPath. 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.
Browser-Find-By-XPath 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 →