[LEGACY] Interact with a page element. Use interact_with_page instead.
AI agents invoke interact_with_element to trigger actions in ZMCPTools. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Browser element interaction executes real actions in a live browser (clicks, form submissions, input changes) whose effects depend on the target element and context. This falls under Execute as it triggers external operations. Severity is high because misuse could submit forms, trigger purchases, or perform unintended UI actions.
From the tool's definition "Interact with a page element" and "browser automation" context from server description — triggers UI actions (clicks, inputs, etc.) on live web elements
Documented attack patterns abuse exactly the kind of access interact_with_element gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ZMCPTools, and nothing reaches the server without passing your rules. This is the rule we recommend for interact_with_element:
{
"version": "1",
"default": "deny",
"tools": {
"interact_with_element": {
"limits": [
{
"counter": "interact_with_element_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}interact_with_element stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
[LEGACY] Interact with a page element. Use interact_with_page instead. It is categorised as a Execute tool in the ZMCPTools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ZMCPTools MCP server in PolicyLayer and add a rule for interact_with_element: 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 ZMCPTools. Nothing to install.
interact_with_element is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the interact_with_element 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 interact_with_element. 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.
interact_with_element is provided by the ZMCPTools MCP server (zachhandley/zmcptools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 70 ZMCPTools tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
70 ZMCPTools tools catalogued and risk-classified — across an index of 42,500+ MCP servers.