test_detect

Detect an installed GDScript test framework (GUT or GdUnit4) in the project. Returns { framework: gut|gdunit4|none, path, version }. Read-only.

SERVERBreakpoint SOURCEbreakpoint-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/breakpoint-mcp/test-detect.md

WHAT IT DOES

What test_detect does on Breakpoint

AI agents call test_detect 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.

RISK

Why test_detect is rated Low

This tool retrieves information about installed test frameworks in a project without side effects. It queries the state of the project environment to determine which testing framework is present and provides metadata about it. This is a straightforward read operation with negligible security risk.

From the tool's definition Tool description explicitly states 'Read-only' and describes detecting/querying test framework information (returns framework name, path, version). No modification, deletion, or execution is performed.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs test_detect 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_detect, this is the rule to start with:

test_detect Allowed

test_detect 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_detect": {}
  }
}

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

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

FAQ

Questions about test_detect

What does the test_detect tool do? +

Detect an installed GDScript test framework (GUT or GdUnit4) in the project. Returns { framework: gut|gdunit4|none, path, version }. Read-only. It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on test_detect? +

Register the Breakpoint MCP server in PolicyLayer and add a rule for test_detect: 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.

What risk level is test_detect? +

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

Can I rate-limit test_detect? +

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

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

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

KEEP EXPLORING

More on Breakpoint, and thousands of servers like it.

This server

All 274 Breakpoint tools →

Across the catalogue

detect_slop on Slop Cop → The MCP Attack Database →

Guides

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