test_list

List GDScript test scripts (files named test_*.gd or *_test.gd) under a directory (default res://test), searched recursively. Read-only.

SERVERGodot Breakpoint SOURCEjlivingston-Cipher/godot-breakpoint-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/godot-breakpoint-mcp/test-list.md

WHAT IT DOES

What test_list does on Godot Breakpoint

AI agents call test_list to retrieve information from Godot Breakpoint without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why test_list is rated Low

This tool performs a non-destructive query/retrieval operation—listing files matching a naming pattern in a directory tree. It has no capacity to modify, delete, execute, or cause side effects. The 'Read-only' designation and the verb 'list' confirm it belongs in the Read category. Severity is low because miscalling this tool poses minimal risk (worst case: information disclosure of test file names).

From the tool's definition Tool description explicitly states it 'List[s] GDScript test scripts' and is marked 'Read-only'. The action is a passive directory search with no modifications, side effects, or execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs test_list safely

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

test_list Allowed

test_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "test_list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about test_list

What does the test_list tool do? +

List GDScript test scripts (files named test_*.gd or *_test.gd) under a directory (default res://test), searched recursively. Read-only. It is categorised as a Read tool in the Godot Breakpoint MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on test_list? +

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

What risk level is test_list? +

test_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit test_list? +

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

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

test_list is provided by the Godot Breakpoint MCP server (jlivingston-Cipher/godot-breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Godot Breakpoint, and thousands of servers like it.

This server

All 239 Godot Breakpoint tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →