swagger_update_portal

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Medium RISK CLASS

Category Write

Parameters 101 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/smartbear-mcp/swagger-update-portal.md

WHAT IT DOES

What swagger_update_portal does on SmartBear MCP

AI agents use swagger_update_portal 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 the portal display name - shown to users and in branding (3-40 characters)
`gtmKey`	string	—	Google Tag Manager key for analytics tracking - format: GTM-XXXXXX (max 25 characters)
`offline`	boolean	—	Set portal visibility - true hides portal from customers (useful for maintenance or development)
`routing`	string	—	Update routing strategy - 'browser' for client-side routing or 'proxy' for server-side routing
`portalId`	string	Yes	Portal UUID or subdomain - unique identifier for the portal instance
`subdomain`	string	—	Update the portal subdomain - changes the portal URL. Must remain unique across all portals (3-20 characters, lowercase, alphanumeric with hyphens)
`customDomain`	boolean	—	Enable/disable custom domain for the portal - allows using your own domain instead of the default subdomain
`openapiRenderer`	string	—	Change OpenAPI renderer: 'SWAGGER_UI' (Swagger UI), 'ELEMENTS' (Stoplight Elements), or 'TOGGLE' (switch between both)
`pageContentFormat`	string	—	Update page content format for documentation rendering: 'HTML', 'MARKDOWN', or 'BOTH'
`credentialsEnabled`	boolean	—	Enable/disable authentication credentials for portal access - controls whether users can authenticate to view private content

Parameters from the server's own tool schema.

RISK

Why swagger_update_portal is rated Medium

This tool creates or modifies data (portal settings) in a reversible manner. While subdomain changes affect the portal URL and could impact users, the operation is not irreversible—configurations can be changed back.

From the tool's definition The tool 'swagger_update_portal' modifies portal configuration including name, subdomain, customDomain, and gtmKey. The description explicitly states 'Update a specific portal's configuration,' which is a reversible modification operation.

Risk signalsHigh parameter count (10 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs swagger_update_portal 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, this is the rule to start with:

swagger_update_portal Rate-limited

swagger_update_portal 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "swagger_update_portal": {
      "limits": [
        {
          "counter": "swagger_update_portal_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect SmartBear MCP, apply this rule, and every swagger_update_portal call is checked against it from then on.

FAQ

Questions about swagger_update_portal

What does the swagger_update_portal tool do? +

Update a specific portal's configuration. Parameters: - portalId (string) *required*: Portal UUID or subdomain - unique identifier for the portal instance - name (string): Update the portal display name - shown to users and in branding (3-40 characters) - subdomain (string): Update the portal subdomain - changes the portal URL. Must remain unique across all portals (3-20 characters, lowercase, alphanumeric with hyphens) - customDomain (boolean): Enable/disable custom domain for the portal - allows using your own domain instead of the default subdomain - gtmKey (string): Google Tag Manager key for analytics tracking - format: GTM-XXXXXX (max 25 characters) - offline (boolean): Set portal visibility - true hides portal from customers (useful for maintenance or development) - routing (string): Update routing strategy - 'browser' for client-side routing or 'proxy' for server-side routing - credentialsEnabled (boolean): Enable/disable authentication credentials for portal access - controls whether users can authenticate to view private content - openapiRenderer (string): Change OpenAPI renderer: 'SWAGGER_UI' (Swagger UI), 'ELEMENTS' (Stoplight Elements), or 'TOGGLE' (switch between both) - pageContentFormat (string): Update page content format for documentation rendering: 'HTML', 'MARKDOWN', or 'BOTH'. 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.

What parameters does swagger_update_portal accept? +

swagger_update_portal accepts 10 parameters: name, gtmKey, offline, routing, portalId, subdomain, customDomain, openapiRenderer, pageContentFormat, credentialsEnabled. Required: portalId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on swagger_update_portal? +

Register the SmartBear MCP server in PolicyLayer and add a rule for swagger_update_portal: 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 swagger_update_portal? +

swagger_update_portal is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit swagger_update_portal? +

Yes. Add a rate_limit block to the swagger_update_portal 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 swagger_update_portal completely? +

Set action: deny in the PolicyLayer policy for swagger_update_portal. 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 swagger_update_portal? +

swagger_update_portal 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.

KEEP EXPLORING

More on SmartBear, and thousands of servers like it.

This server

All 240 SmartBear tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →