manage_shader · GameDevBench MCP: Risk & Policy

WHAT IT DOES

What manage_shader does on GameDevBench MCP

AI agents use manage_shader to create or update resources in GameDevBench MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GameDevBench MCP environment.

WHY IT NEEDS A POLICY

Why manage_shader needs a policy

The tool name 'manage_shader' suggests CRUD operations on shaders in the Godot game engine context. 'Manage' most commonly implies write operations (create/update), though it could also include delete (destructive). Given sibling tools like 'create_script' and 'delete_script' exist separately, 'manage_shader' likely covers multiple shader operations.

From the tool's definition Tool name 'manage_shader' with empty description. 'manage' typically implies create/update/delete operations on shader resources.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

manage_shader Rate-limited

manage_shader stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "manage_shader": {
      "limits": [
        {
          "counter": "manage_shader_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 manage_shader

What does the manage_shader tool do? +

manage_shader. It is categorised as a Write tool in the GameDevBench MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on manage_shader? +

Register the GameDevBench MCP server in PolicyLayer and add a rule for manage_shader: 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 manage_shader? +

manage_shader is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit manage_shader? +

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

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

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