test_status

THE RISK

Low Risk

Why test_status needs a policy

This tool queries and reports on the state of project tests without creating, modifying, deleting, executing code, or committing financial obligations. It is a pure information-retrieval operation with minimal blast radius if misused.

From the tool's definition Tool name 'test_status' and description 'Get project test status and recommendations' indicate retrieval of test information with no modification or side effects.

Documented attack patterns abuse exactly the kind of access test_status gives an agent:

POLICY

How to control test_status

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP DevTools Server, and nothing reaches the server without passing your rules. This is the rule we recommend for test_status:

policy.json

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

test_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register MCP DevTools Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP DevTools Server tools

Destructive repo_sync Sync with remote and cleanup merged branches Execute python_venv Manage Python virtual environments (create, delete, info, list packages) Execute commitlint Run commitlint to validate commit messages Execute eslint Run ESLint on JavaScript/TypeScript files Execute go_benchmark Run Go benchmarks to measure code performance Execute go_build Build Go packages with cross-compilation and custom build flags support Execute lint_all Run all available linters based on project type Execute lint_files Run custom linting rules on project files

All 79 MCP DevTools Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about test_status

What does the test_status tool do? +

Get project test status and recommendations. It is categorised as a Read tool in the MCP DevTools Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on test_status? +

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

What risk level is test_status? +

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

Can I rate-limit test_status? +

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

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

test_status is provided by the MCP DevTools Server MCP server (rshade/mcp-devtools-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP DevTools Server tool call.

Start from MCP DevTools Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →