High Risk

reflect_run_test

Run a reflect test **Parameters:** - testId (string) *required*: ID of the reflect test to run

Part of the SmartBear MCP MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@smartbear/mcp Execute Risk 3/5

AI agents invoke reflect_run_test to trigger processes or run actions in SmartBear MCP. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

reflect_run_test can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

smartbear-mcp.yaml
tools:
  reflect_run_test:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full SmartBear MCP policy for all 147 tools.

Tool Name reflect_run_test
Category Execute
Risk Level High

View all 147 tools →

What does the reflect_run_test tool do? +

Run a reflect test **Parameters:** - testId (string) *required*: ID of the reflect test to run. It is categorised as a Execute tool in the SmartBear MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on reflect_run_test? +

Add a rule in your Intercept YAML policy under the tools section for reflect_run_test. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the SmartBear MCP MCP server.

What risk level is reflect_run_test? +

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

Can I rate-limit reflect_run_test? +

Yes. Add a rate_limit block to the reflect_run_test rule in your Intercept 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 reflect_run_test completely? +

Set action: deny in the Intercept policy for reflect_run_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 reflect_run_test? +

reflect_run_test is provided by the SmartBear MCP MCP server (@smartbear/mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on SmartBear MCP

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.