获取当前标签页中所有指定tagname的元素信息,定位元素时优先使用 ，参数是tagname
AI agents call get_elements_info_by_tagname 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 tool queries and retrieves DOM element information without modifying, executing, or deleting any data. It is a passive information-gathering operation analogous to 'get' or 'list' operations. While it operates within a browser automation context, the specific action is pure data retrieval with no side effects.
From the tool's definition Tool name 'get_elements_info_by_tagname' and description indicate it retrieves element information by tag name from the current page.
Documented attack patterns abuse exactly the kind of access get_elements_info_by_tagname 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 get_elements_info_by_tagname:
{
"version": "1",
"default": "deny",
"tools": {
"get_elements_info_by_tagname": {}
}
}get_elements_info_by_tagname 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.
获取当前标签页中所有指定tagname的元素信息,定位元素时优先使用 ，参数是tagname. 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 get_elements_info_by_tagname: 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.
get_elements_info_by_tagname 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_elements_info_by_tagname 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_elements_info_by_tagname. 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_elements_info_by_tagname 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.