benchmark · Uitars MCP: Risk & Policy

WHAT IT DOES

What benchmark does on Uitars

AI agents invoke benchmark to trigger actions in Uitars. 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 benchmark needs a policy

Benchmarking here involves executing real operations (screenshot capture and vision model inference) to measure latency. It's not purely reading stored data; it actively triggers external operations. No data is written, deleted, or financial in nature. The blast radius is low since it's a measurement/diagnostic tool with no side effects beyond resource consumption.

From the tool's definition 'Benchmark end-to-end latency (screenshot + inference)' — triggers active operations: takes a screenshot and runs model inference

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

benchmark Rate-limited

benchmark 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": {
    "benchmark": {
      "limits": [
        {
          "counter": "benchmark_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 Uitars, so you can run agents against it safely.

FAQ

Questions about benchmark

What does the benchmark tool do? +

Benchmark end-to-end latency (screenshot + inference). It is categorised as a Execute tool in the Uitars MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on benchmark? +

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

What risk level is benchmark? +

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

Can I rate-limit benchmark? +

Yes. Add a rate_limit block to the benchmark 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 benchmark completely? +

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

benchmark is provided by the Uitars MCP server (lxsoftroxs/uitars-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.