AI agents call is_element_exist to retrieve information from DrissionPageMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only introspection tool. It queries the presence of page elements but does not click, input, execute scripts, delete, or cause side effects. Despite the browser automation context, this specific tool only retrieves information about element presence and should be classified as Read with low severity.
From the tool's definition Tool checks whether an element exists in a page via xpath or keyword matching in text nodes—'is_element_exist' performs a query/inspection of DOM state without modifying, executing code, or triggering external operations.
Documented attack patterns abuse exactly the kind of access is_element_exist gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DrissionPageMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for is_element_exist:
{
"version": "1",
"default": "deny",
"tools": {
"is_element_exist": {}
}
}is_element_exist is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
通过xpath或者文本节点是否包含关键词判断标签页中某个元素是否存在. It is categorised as a Read tool in the DrissionPageMCP MCP Server, which means it retrieves data without modifying state.
Register the DrissionPage MCP server in PolicyLayer and add a rule for is_element_exist: 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 DrissionPageMCP. Nothing to install.
is_element_exist 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 is_element_exist 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 is_element_exist. 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.
is_element_exist is provided by the DrissionPage MCP server (wxhzhwxhzh/drissionpagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 37 DrissionPageMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
37 DrissionPageMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.