run_functional_tests · Springboot Test MCP: Risk & Policy

WHAT IT DOES

What run_functional_tests does on Springboot Test

AI agents invoke run_functional_tests to trigger actions in Springboot 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 run_functional_tests needs a policy

This tool runs functional tests, which inherently executes code and triggers external operations (API calls, database operations, assertions). While it operates within a testing context and is not directly destructive, it can execute arbitrary test logic including database modifications via sibling 'execute_dml' tool and external API interactions via 'call_api'.

From the tool's definition Tool name 'run_functional_tests' combined with sibling tools that include 'execute_dml', 'query_database', 'assert_response', and 'call_api' indicate this tool triggers test execution workflows.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_functional_tests Rate-limited

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

FAQ

Questions about run_functional_tests

What does the run_functional_tests tool do? +

run_functional_tests. It is categorised as a Execute tool in the Springboot 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 run_functional_tests? +

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

What risk level is run_functional_tests? +

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

Can I rate-limit run_functional_tests? +

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

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

run_functional_tests is provided by the Springboot Test MCP server (kenlin-7/springboot-test-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.