swagger_search_apis_and_domains
Search for APIs and Domains in SwaggerHub Registry using the comprehensive /specs endpoint and retrieve metadata including owner, name, description, summary, version, and specification. Parameters: - query (string): Search query to filter APIs by name, description, or content - state (enum): Filt...
This record as markdown: /tools/smartbear-mcp/swagger-search-apis-and-domains.md
What swagger_search_apis_and_domains does on SmartBear MCP
AI agents call swagger_search_apis_and_domains 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
tag | string | — | Filter APIs by tag |
sort | string | — | Sort field - NAME, UPDATED, or CREATED (default NAME) |
limit | number | — | Number of results per page (1-100, default 20) |
order | string | — | Sort order - ASC or DESC (default ASC) |
owner | string | — | Filter APIs by owner (organization or user) |
query | string | — | Search query to filter APIs by name, description, or content |
state | string | — | Filter APIs by publication state - ALL (default), PUBLISHED, or UNPUBLISHED |
offset | number | — | Offset for pagination (0-based, default 0) |
specType | string | — | Filter by specification type - API or DOMAIN (default all types) |
Parameters from the server's own tool schema.
Why swagger_search_apis_and_domains is rated Low
This tool performs read-only queries against a SwaggerHub registry to retrieve API metadata. It has no side effects—it only searches and retrieves information. No write, delete, execute, or financial operations are possible. The blast radius of misuse is minimal, limited to information disclosure of API specifications and metadata already in a registry.
From the tool's definition Tool description states it 'Search for APIs and Domains' and 'retrieve metadata including owner, name, description, summary, version, and specification.' Parameters enable filtering and pagination but no modification, deletion, or execution capability is…
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
The rule that runs swagger_search_apis_and_domains 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_search_apis_and_domains, this is the rule to start with:
swagger_search_apis_and_domains 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_search_apis_and_domains call is checked against it from then on.
Questions about swagger_search_apis_and_domains
Search for APIs and Domains in SwaggerHub Registry using the comprehensive /specs endpoint and retrieve metadata including owner, name, description, summary, version, and specification. Parameters: - query (string): Search query to filter APIs by name, description, or content - state (enum): Filter APIs by publication state - ALL (default), PUBLISHED, or UNPUBLISHED - tag (string): Filter APIs by tag - offset (number): Offset for pagination (0-based, default 0) - limit (number): Number of results per page (1-100, default 20) - sort (enum): Sort field - NAME, UPDATED, or CREATED (default NAME) - order (enum): Sort order - ASC or DESC (default ASC) - owner (string): Filter APIs by owner (organization or user) - specType (enum): Filter by specification type - API or DOMAIN (default all types). It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.
swagger_search_apis_and_domains accepts 9 parameters: tag, sort, limit, order, owner, query, state, offset, specType. 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_search_apis_and_domains: 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_search_apis_and_domains 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_search_apis_and_domains 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_search_apis_and_domains. 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_search_apis_and_domains 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