evaluate_web_task · Blop MCP: Risk & Policy

WHAT IT DOES

What evaluate_web_task does on Blop

AI agents invoke evaluate_web_task to trigger actions in Blop. 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.

WHY IT NEEDS A POLICY

Why evaluate_web_task needs a policy

The tool name 'evaluate_web_task' implies executing or evaluating a task in a web/browser context. Given the server's stated purpose of 'browser execution' and sibling tools strongly associated with browser automation and testing, this tool likely triggers browser-based actions. Description is empty, which lowers confidence, but the surrounding context points to Execute category.

From the tool's definition Tool name 'evaluate_web_task' combined with server description mentioning 'browser execution' and sibling tools like 'get_page_snapshot', 'capture_auth_session', 'debug_test_case' suggesting browser automation context.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

evaluate_web_task Rate-limited

evaluate_web_task 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "evaluate_web_task": {
      "limits": [
        {
          "counter": "evaluate_web_task_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Blop, so you can run agents against it safely.

FAQ

Questions about evaluate_web_task

What does the evaluate_web_task tool do? +

evaluate_web_task. It is categorised as a Execute tool in the Blop MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on evaluate_web_task? +

Register the Blop MCP server in PolicyLayer and add a rule for evaluate_web_task: 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 Blop. Nothing to install.

What risk level is evaluate_web_task? +

evaluate_web_task is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit evaluate_web_task? +

Yes. Add a rate_limit block to the evaluate_web_task 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.

How do I block evaluate_web_task completely? +

Set action: deny in the PolicyLayer policy for evaluate_web_task. 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.

What MCP server provides evaluate_web_task? +

evaluate_web_task is provided by the Blop MCP server (n2400813g/blop-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.