Poll for browsing task status and result. Call until status is
AI agents call get_browsing_task_result to retrieve information from Yutori MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves status and results from an already-running browsing task. It performs no modifications, deletions, or execution — it only reads the state and output of a task that was triggered elsewhere (likely via run_browsing_task). Polling for results is a classic Read operation with minimal blast radius.
From the tool's definition Tool description explicitly states 'Poll for browsing task status and result' — this is a query/polling operation retrieving the result of a previously initiated task. The verb 'get' and 'poll' indicate data retrieval with no side effects.
Documented attack patterns abuse exactly the kind of access get_browsing_task_result gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Yutori MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_browsing_task_result:
{
"version": "1",
"default": "deny",
"tools": {
"get_browsing_task_result": {}
}
} get_browsing_task_result 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.
Poll for browsing task status and result. Call until status is. It is categorised as a Read tool in the Yutori MCP MCP Server, which means it retrieves data without modifying state.
Register the Yutori MCP server in PolicyLayer and add a rule for get_browsing_task_result: 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 Yutori MCP. Nothing to install.
get_browsing_task_result 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_browsing_task_result 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_browsing_task_result. 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_browsing_task_result is provided by the Yutori MCP server (yutori-ai/yutori-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Yutori MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
11 Yutori MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.