reflect_add_segment
Insert a reusable test segment into an active Reflect recording session Parameters: - sessionId (string) *required*: The ID of the Reflect recording session - segmentId (number) *required*: The ID of the segment to add
This record as markdown: /tools/smartbear-mcp/reflect-add-segment.md
What reflect_add_segment does on SmartBear MCP
AI agents use reflect_add_segment to create or update resources in SmartBear MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SmartBear MCP environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
segmentId | number | Yes | The ID of the segment to add |
sessionId | string | Yes | The ID of the Reflect recording session |
Parameters from the server's own tool schema.
Why reflect_add_segment is rated Medium
This tool creates/adds a test segment to a recording session, which is a reversible modification of data. It does not execute arbitrary code, delete data irreversibly, or move money. While it modifies an active session (which could affect testing workflows if misused), the operation is reversible by removing the segment.
From the tool's definition The tool description states it will 'Insert a reusable test segment into an active Reflect recording session.' The verb 'Insert' combined with modifying an active recording session indicates a write operation that creates or adds data to an existing resource.
Attacks that exploit this kind of access
The rule that runs reflect_add_segment 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_add_segment, this is the rule to start with:
reflect_add_segment stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_add_segment call is checked against it from then on.
Questions about reflect_add_segment
Insert a reusable test segment into an active Reflect recording session Parameters: - sessionId (string) *required*: The ID of the Reflect recording session - segmentId (number) *required*: The ID of the segment to add. It is categorised as a Write tool in the SmartBear MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
reflect_add_segment accepts 2 parameters: segmentId, sessionId. Required: segmentId, sessionId. 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_add_segment: 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_add_segment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the reflect_add_segment 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_add_segment. 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_add_segment 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