reflect_run_test

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

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp
High RISK CLASS
Category Execute
Parameters 11 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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…

Questions about reflect_run_test

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.

What parameters does reflect_run_test accept? +

reflect_run_test accepts 1 parameter: testId. Required: testId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on reflect_run_test? +

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.

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 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 reflect_run_test completely? +

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.

What MCP server provides reflect_run_test? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of SmartBear's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.