test_list
List GDScript test scripts (files named test_*.gd or *_test.gd) under a directory (default res://test), searched recursively. Read-only.
This record as markdown: /tools/breakpoint-mcp/test-list.md
What test_list does on Breakpoint
AI agents call test_list to retrieve information from Breakpoint without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
dir | string | — | Directory to search (default res://test) |
Parameters from the server's own tool schema.
Why test_list is rated Low
This tool retrieves and lists test script files from a specified directory without modifying, creating, or deleting any data. It is a straightforward read operation with minimal security risk, as it only enumerates existing files in a controlled test directory.
From the tool's definition Tool description explicitly states 'List GDScript test scripts' and 'Read-only'. The verb 'List' and qualifier 'Read-only' clearly indicate data retrieval with no side effects.
Risk signalsAccepts file system path (dir)
Attacks that exploit this kind of access
The rule that runs test_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 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 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every test_list call is checked against it from then on.
Questions about test_list
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 Breakpoint MCP Server, which means it retrieves data without modifying state.
test_list accepts 1 parameter: dir. The full parameter table on this page comes from the server's own tool schema.
Register the 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 Breakpoint. Nothing to install.
test_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
test_list is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
This server
Across the catalogue