swagger_create_portal

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Medium RISK CLASS

Category Write

Parameters 82 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What swagger_create_portal does on SmartBear MCP

AI agents use swagger_create_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	—	The display name for the portal - shown to users and in branding (3-40 characters)
`offline`	boolean	—	If true, the portal will not be visible to customers - useful for development/staging environments. Defaults to false
`routing`	string	—	Routing strategy for the portal - either 'browser' (client-side routing) or 'proxy' (server-side routing). Defaults to 'browser'
`subdomain`	string	Yes	The portal subdomain - used in the portal URL (e.g., 'myportal' for myportal.example.com). Must be unique, lowercase, 3-20 characters, alphanumeric with hyphens
`openapiRenderer`	string	—	OpenAPI renderer type: 'SWAGGER_UI' (Swagger UI), 'ELEMENTS' (Stoplight Elements), or 'TOGGLE' (allows switching between both with Elements as default). Default
`pageContentFormat`	string	—	Format for page content rendering - determines how documentation pages are processed: 'HTML', 'MARKDOWN', or 'BOTH'. Defaults to 'HTML'
`credentialsEnabled`	boolean	—	Whether authentication credentials are enabled for accessing the portal. When true, users can authenticate to access private content. Defaults to true
`swaggerHubOrganizationId`	string	Yes	The corresponding SwaggerHub organization UUID - required for portal creation. This links the portal to your SwaggerHub organization

Parameters from the server's own tool schema.

RISK

Why swagger_create_portal is rated Medium

This tool creates a new portal resource, which is a reversible write operation. It does not retrieve data (Read), execute arbitrary code (Execute), permanently delete data (Destructive), or move money (Financial). The blast radius is medium because portal creation could impact system organization, visibility settings, and routing configuration, but the action can be undone by deleting the portal.

From the tool's definition Tool name 'swagger_create_portal' and description 'Create a new portal within Swagger' indicate the tool creates and adds new resources to the system. Parameters like 'name', 'subdomain', and 'offline' are configuration inputs for a new entity creation.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

swagger_create_portal Rate-limited

swagger_create_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_create_portal": {
      "limits": [
        {
          "counter": "swagger_create_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_create_portal call is checked against it from then on.

FAQ

Questions about swagger_create_portal

What does the swagger_create_portal tool do? +

Create a new portal within Swagger. Parameters: - name (string): The display name for the portal - shown to users and in branding (3-40 characters) - subdomain (string) *required*: The portal subdomain - used in the portal URL (e.g., 'myportal' for myportal.example.com). Must be unique, lowercase, 3-20 characters, alphanumeric with hyphens - offline (boolean): If true, the portal will not be visible to customers - useful for development/staging environments. Defaults to false - routing (string): Routing strategy for the portal - either 'browser' (client-side routing) or 'proxy' (server-side routing). Defaults to 'browser' - credentialsEnabled (boolean): Whether authentication credentials are enabled for accessing the portal. When true, users can authenticate to access private content. Defaults to true - swaggerHubOrganizationId (string) *required*: The corresponding SwaggerHub organization UUID - required for portal creation. This links the portal to your SwaggerHub organization - openapiRenderer (string): OpenAPI renderer type: 'SWAGGER_UI' (Swagger UI), 'ELEMENTS' (Stoplight Elements), or 'TOGGLE' (allows switching between both with Elements as default). Defaults to 'TOGGLE' - pageContentFormat (string): Format for page content rendering - determines how documentation pages are processed: 'HTML', 'MARKDOWN', or 'BOTH'. Defaults to 'HTML'. 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_create_portal accept? +

swagger_create_portal accepts 8 parameters: name, offline, routing, subdomain, openapiRenderer, pageContentFormat, credentialsEnabled, swaggerHubOrganizationId. Required: subdomain, swaggerHubOrganizationId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on swagger_create_portal? +

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

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

Can I rate-limit swagger_create_portal? +

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

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

swagger_create_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

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

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