run_api_test · Sentinel MCP: Risk & Policy

WHAT IT DOES

What run_api_test does on Sentinel

AI agents invoke run_api_test to trigger actions in Sentinel. 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 run_api_test needs a policy

This tool executes automated test operations against API endpoints, which is an active operation that triggers external behavior. Although the tests themselves are non-destructive exploratory operations, they execute code and have side effects on target systems (network requests, state changes from test data).

From the tool's definition The tool description states it will "Run positive and negative functional tests on API endpoints" and "AI generates test cases automatically".

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_api_test Rate-limited

run_api_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": {
    "run_api_test": {
      "limits": [
        {
          "counter": "run_api_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 Sentinel, so you can run agents against it safely.

FAQ

Questions about run_api_test

What does the run_api_test tool do? +

Run positive and negative functional tests on API endpoints. AI generates test cases automatically and analyzes results. It is categorised as a Execute tool in the Sentinel MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_api_test? +

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

What risk level is run_api_test? +

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

Can I rate-limit run_api_test? +

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

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

run_api_test is provided by the Sentinel MCP server (kal72/sentinel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.