list_web_tasks
AI agents call list_web_tasks to retrieve information from Gemini Web Automation MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears designed to retrieve or enumerate active web automation tasks for status checking or management visibility. While the empty description reduces confidence slightly, the naming pattern and context among sibling tools (which include state-checking operations like check_web_task and get_web_screenshots) suggest this is a read-only query operation with no side effects on the underlying tasks or data.
From the tool's definition Tool name 'list_web_tasks' and sibling tools (browse_web, check_web_task, get_web_screenshots, start_web_task, stop_web_task, wait) indicate this is a monitoring/query tool. The 'list' prefix strongly suggests retrieval without modification.
Attacks that exploit this kind of access
list_web_tasks. It is categorised as a Read tool in the Gemini Web Automation MCP MCP Server, which means it retrieves data without modifying state.
Register the Gemini Web Automation MCP server in PolicyLayer and add a rule for list_web_tasks: 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 Gemini Web Automation MCP. Nothing to install.
list_web_tasks 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 list_web_tasks 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 list_web_tasks. 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.
list_web_tasks is provided by the Gemini Web Automation MCP server (vincenthopf/computer-use-mcp). 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 →