Get full details of a specific task. Args: task_id: Task ID (full or prefix) Returns: JSON object with task details, input, and result/error
AI agents call task_get to retrieve information from Browser-Use MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries task information by ID. It performs a read-only lookup operation that returns existing task details without creating, modifying, deleting, or executing any operations. The only argument is a task_id used for filtering, presenting no capability for side effects.
From the tool's definition Tool name 'task_get' and description 'Get full details of a specific task' with return of 'JSON object with task details' indicates data retrieval with no modification or execution.
Documented attack patterns abuse exactly the kind of access task_get gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Browser-Use MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for task_get:
{
"version": "1",
"default": "deny",
"tools": {
"task_get": {}
}
}task_get 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.
Get full details of a specific task. Args: task_id: Task ID (full or prefix) Returns: JSON object with task details, input, and result/error. It is categorised as a Read tool in the Browser-Use MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Browser-Use MCP Server MCP server in PolicyLayer and add a rule for task_get: 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 Browser-Use MCP Server. Nothing to install.
task_get 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 task_get 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 task_get. 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.
task_get is provided by the Browser-Use MCP Server MCP server (saik0s/mcp-browser-use). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 9 Browser-Use MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
9 Browser-Use MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.