AI agents call getInputElementsInfo 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 returns metadata about input elements available on a webpage—a read-only operation with no side effects. It gathers information to inform subsequent actions but does not itself modify state, execute code, or interact with elements. The low severity reflects minimal risk if misused in isolation, as it only exposes element information already visible in the DOM.
From the tool's definition Tool name 'getInputElementsInfo' and description indicating it retrieves information about input elements on the current page ('获取当前标签页的所有可进行输入操作的元素').
Documented attack patterns abuse exactly the kind of access getInputElementsInfo 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 getInputElementsInfo:
{
"version": "1",
"default": "deny",
"tools": {
"getInputElementsInfo": {}
}
}getInputElementsInfo 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.
获取当前标签页的所有可进行输入操作的元素，对元素进行输入操作前优先使用这个方法. 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 getInputElementsInfo: 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.
getInputElementsInfo 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 getInputElementsInfo 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 getInputElementsInfo. 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.
getInputElementsInfo 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.