swagger_list_portals
Search for available portals within Swagger. Only portals where you have at least a designer role, either at the product level or organization level, are returned.
This record as markdown: /tools/smartbear-mcp/swagger-list-portals.md
What swagger_list_portals does on SmartBear MCP
AI agents call swagger_list_portals 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.
Why swagger_list_portals is rated Low
This tool retrieves and lists available Swagger portals that the user has access to (designer role or above). It performs a query operation that returns data without modifying, executing, or deleting anything. The only data exposed is a list of portals the authenticated user already has permissions to see. This is a standard read/search operation with minimal security impact.
From the tool's definition Tool name is 'swagger_list_portals' and description states it 'Search for available portals' and 'are returned'. The verb 'search' and 'list' combined with 'returns' information indicates a read-only query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs swagger_list_portals 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_list_portals, this is the rule to start with:
swagger_list_portals 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 swagger_list_portals call is checked against it from then on.
Questions about swagger_list_portals
Search for available portals within Swagger. Only portals where you have at least a designer role, either at the product level or organization level, are returned. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.
Register the SmartBear MCP server in PolicyLayer and add a rule for swagger_list_portals: 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_list_portals 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 swagger_list_portals 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_list_portals. 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_list_portals 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