swagger_update_portal_product
Update a product's settings within a specific portal. Parameters: - productId (string) *required*: Product UUID or identifier in the format 'portal-subdomain:product-slug' - unique identifier for the product - name (string): Update product display name - changes how it appears to users in navigat...
This record as markdown: /tools/smartbear-mcp/swagger-update-portal-product.md
What swagger_update_portal_product does on SmartBear MCP
AI agents use swagger_update_portal_product 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 |
|---|---|---|---|
name | string | — | Update product display name - changes how it appears to users in navigation and listings (3-40 characters) |
slug | string | — | Update URL-friendly identifier - must remain unique within the portal, affects product URLs (3-22 characters, lowercase, alphanumeric with hyphens/underscores/d |
hidden | boolean | — | Change navigation visibility - true hides from portal landing page menus while keeping the product accessible via direct links |
public | boolean | — | Change product visibility - true makes it publicly accessible to all visitors, false restricts to authenticated users with roles |
productId | string | Yes | Product UUID or identifier in the format 'portal-subdomain:product-slug' - unique identifier for the product |
description | string | — | Update product description - explains the API/product functionality, shown in listings (max 110 characters) |
Parameters from the server's own tool schema.
Why swagger_update_portal_product is rated Medium
This tool creates or modifies data reversibly. It updates product metadata (name, slug, description) within a portal, which are configuration changes that can be undone or modified again. The impact is limited to product configuration settings rather than destructive data loss or code execution.
From the tool's definition Tool name includes 'update', description states 'Update a product's settings within a specific portal'. Parameters allow modification of product name, slug, description, and other settings.
Attacks that exploit this kind of access
The rule that runs swagger_update_portal_product 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 swagger_update_portal_product, this is the rule to start with:
swagger_update_portal_product 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 swagger_update_portal_product call is checked against it from then on.
Questions about swagger_update_portal_product
Update a product's settings within a specific portal. Parameters: - productId (string) *required*: Product UUID or identifier in the format 'portal-subdomain:product-slug' - unique identifier for the product - name (string): Update product display name - changes how it appears to users in navigation and listings (3-40 characters) - slug (string): Update URL-friendly identifier - must remain unique within the portal, affects product URLs (3-22 characters, lowercase, alphanumeric with hyphens/underscores/dots) - description (string): Update product description - explains the API/product functionality, shown in listings (max 110 characters) - public (boolean): Change product visibility - true makes it publicly accessible to all visitors, false restricts to authenticated users with roles - hidden (boolean): Change navigation visibility - true hides from portal landing page menus while keeping the product accessible via direct links. 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.
swagger_update_portal_product accepts 6 parameters: name, slug, hidden, public, productId, description. Required: productId. 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 swagger_update_portal_product: 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.
swagger_update_portal_product 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 swagger_update_portal_product 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 swagger_update_portal_product. 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.
swagger_update_portal_product 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