reflect_run_test
Run a reflect test Parameters: - testId (string) *required*: ID of the reflect test to run
This record as markdown: /tools/smartbear-mcp/reflect-run-test.md
What reflect_run_test does on SmartBear MCP
AI agents invoke reflect_run_test to trigger actions in SmartBear MCP. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
testId | string | Yes | ID of the reflect test to run |
Parameters from the server's own tool schema.
Why reflect_run_test is rated High
This tool triggers execution of an external test operation whose side effects are unknown and determined by test configuration. Test suites commonly make API calls, modify data, or interact with external systems. While not inherently destructive or financial, it represents arbitrary code/operation execution that an AI agent could misuse by running unintended tests with unknown consequences.
From the tool's definition Tool name 'reflect_run_test' with description 'Run a reflect test' indicates execution of a test suite. The parameter 'testId' specifies which test to execute, but the actual effects depend on what the test performs (API calls, data modifications, external…
Attacks that exploit this kind of access
The rule that runs reflect_run_test safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SmartBear MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reflect_run_test, this is the rule to start with:
reflect_run_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.
The button opens the PolicyLayer dashboard: create your workspace, connect SmartBear MCP, apply this rule, and every reflect_run_test call is checked against it from then on.
Questions about reflect_run_test
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.
reflect_run_test accepts 1 parameter: testId. Required: testId. The full parameter table on this page comes from the server's own tool schema.
Register the SmartBear MCP server in PolicyLayer and add a rule for reflect_run_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 SmartBear MCP. Nothing to install.
reflect_run_test is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the reflect_run_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.
Set action: deny in the PolicyLayer 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.
reflect_run_test is provided by the SmartBear MCP server (SmartBear/smartbear-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on SmartBear, and thousands of servers like it.
Across the catalogue