run_flicker_detection

SERVERNodebench SOURCEnodebench-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-homenshum-nodebench/run-flicker-detection.md

WHAT IT DOES

What run_flicker_detection does on Nodebench

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

RISK

Why run_flicker_detection is rated High

This tool executes a complex, multi-stage diagnostic pipeline on an Android device via ADB (Android Debug Bridge). It runs screen recording, extracts frames, performs image analysis, and generates reports—all operations whose effects depend on runtime arguments and device state.

From the tool's definition Tool performs 'Run full 4-layer Android UI flicker detection pipeline' involving multiple system operations: 'SurfaceFlinger stats', 'screenrecord', 'frame extraction', 'SSIM analysis'.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_flicker_detection safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_flicker_detection, this is the rule to start with:

run_flicker_detection Rate-limited

run_flicker_detection 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": {
    "run_flicker_detection": {
      "limits": [
        {
          "counter": "run_flicker_detection_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every run_flicker_detection call is checked against it from then on.

FAQ

Questions about run_flicker_detection

What does the run_flicker_detection tool do? +

Run full 4-layer Android UI flicker detection pipeline: SurfaceFlinger stats + logcat (L0), screenrecord (L1), frame extraction + SSIM analysis with adaptive threshold (L2), optional semantic verification (L3). Returns FlickerReport with events, SSIM scores, timeline chart, and comparison images. Requires FLICKER_SERVER_URL and adb-connected device. It is categorised as a Execute tool in the Nodebench MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_flicker_detection? +

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

What risk level is run_flicker_detection? +

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

Can I rate-limit run_flicker_detection? +

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

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

run_flicker_detection is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Nodebench, and thousands of servers like it.

This server

All 824 Nodebench tools → High-risk tools on this server →

Across the catalogue

shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →