reflect_list_segments
Retrieve available reusable test segments for the given platform type. Segments are reusable test steps with an optional set of parameters that can used across multiple tests. Parameters: - platform (enum) *required*: The platform type to retrieve segments for - offset (number): Offset for pagina...
This record as markdown: /tools/smartbear-mcp/reflect-list-segments.md
What reflect_list_segments does on SmartBear MCP
AI agents call reflect_list_segments to retrieve information from SmartBear MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Maximum number of segments to return |
offset | number | — | Offset for pagination |
platform | string | Yes | The platform type to retrieve segments for |
Parameters from the server's own tool schema.
Why reflect_list_segments is rated Low
This tool retrieves metadata about test segments for a given platform with optional pagination. It performs a query with no side effects, making it a Read operation. The severity is low because it only exposes informational data about available test segments without access to sensitive information, credentials, or the ability to execute tests or modify data.
From the tool's definition Tool name contains 'list' and description states 'Retrieve available reusable test segments' with read-only parameters (platform, offset, limit for pagination). No mutation, deletion, or execution capabilities described.
Attacks that exploit this kind of access
The rule that runs reflect_list_segments 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_list_segments, this is the rule to start with:
reflect_list_segments is read-only, so it stays allowed. 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_list_segments call is checked against it from then on.
Questions about reflect_list_segments
Retrieve available reusable test segments for the given platform type. Segments are reusable test steps with an optional set of parameters that can used across multiple tests. Parameters: - platform (enum) *required*: The platform type to retrieve segments for - offset (number): Offset for pagination - limit (number): Maximum number of segments to return. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.
reflect_list_segments accepts 3 parameters: limit, offset, platform. Required: platform. 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_list_segments: 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_list_segments is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the reflect_list_segments 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_list_segments. 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_list_segments 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.
This server
Across the catalogue