run_empi_tests · OpenAPI REST MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_empi_tests does on OpenAPI REST MCP Server

AI agents invoke run_empi_tests to trigger actions in OpenAPI REST MCP Server. 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_empi_tests needs a policy

This tool invokes test execution, which is fundamentally a code execution action. While tests are typically read-only by design, execution of arbitrary test suites against a service can have side effects (database state changes, service state modifications, or triggering downstream operations via the tested endpoints).

From the tool's definition Tool runs auto-generated integration tests via 'Run the auto-generated integration tests against the current OpenAPI service.' The tool executes code/test logic against a live service, triggering external operations whose effects depend on test configuration…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_empi_tests Rate-limited

run_empi_tests 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_empi_tests": {
      "limits": [
        {
          "counter": "run_empi_tests_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 OpenAPI REST MCP Server, so you can run agents against it safely.

FAQ

Questions about run_empi_tests

What does the run_empi_tests tool do? +

Run the auto-generated integration tests against the current OpenAPI service. It is categorised as a Execute tool in the OpenAPI REST MCP Server 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_empi_tests? +

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

What risk level is run_empi_tests? +

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

Can I rate-limit run_empi_tests? +

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

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

run_empi_tests is provided by the OpenAPI REST MCP Server MCP server (saranazeer27/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.