sleep_test · Debug Test MCP: Risk & Policy

WHAT IT DOES

What sleep_test does on Debug Test

AI agents invoke sleep_test to trigger actions in Debug Test. 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 sleep_test needs a policy

The tool executes a blocking sleep/wait operation on the server side, which consumes server resources and can intentionally trigger timeout conditions. This is an external operation with side effects (resource consumption, potential denial-of-service via timeout exhaustion), placing it in the Execute category. Misuse could tie up server threads or connections for extended periods.

From the tool's definition 'Sleeps for a specified duration to test timeouts. Use 95+ seconds to trigger timeout.'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sleep_test Rate-limited

sleep_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": {
    "sleep_test": {
      "limits": [
        {
          "counter": "sleep_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 Debug Test, so you can run agents against it safely.

FAQ

Questions about sleep_test

What does the sleep_test tool do? +

Sleeps for a specified duration to test timeouts. Use 95+ seconds to trigger timeout. It is categorised as a Execute tool in the Debug Test MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on sleep_test? +

Register the Debug Test MCP server in PolicyLayer and add a rule for sleep_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 Debug Test. Nothing to install.

What risk level is sleep_test? +

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

Can I rate-limit sleep_test? +

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

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

sleep_test is provided by the Debug Test MCP server (matsjfunke/debug-test-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.