run_playability_test · GameDevBench MCP: Risk & Policy

WHAT IT DOES

What run_playability_test does on GameDevBench MCP

AI agents invoke run_playability_test to trigger actions in GameDevBench MCP. 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 run_playability_test needs a policy

This tool triggers execution of game playability tests within the Godot engine runtime. Even with an empty description, the context of a game development benchmarking server with execution-capable siblings, combined with the action verb 'run', indicates this performs runtime operations.

From the tool's definition Tool name 'run_playability_test' combined with server context indicating Godot game engine interaction and runtime behavior visualization.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_playability_test Rate-limited

run_playability_test 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_playability_test": {
      "limits": [
        {
          "counter": "run_playability_test_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 GameDevBench MCP, so you can run agents against it safely.

FAQ

Questions about run_playability_test

What does the run_playability_test tool do? +

run_playability_test. It is categorised as a Execute tool in the GameDevBench MCP 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_playability_test? +

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

What risk level is run_playability_test? +

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

Can I rate-limit run_playability_test? +

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

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

run_playability_test is provided by the GameDevBench MCP server (seeleai/gamedevbench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.