swagger_get_api_definition

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Low RISK CLASS

Category Read

Parameters 53 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/smartbear-mcp/swagger-get-api-definition.md

WHAT IT DOES

What swagger_get_api_definition does on SmartBear MCP

AI agents call swagger_get_api_definition 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
`api`	string	Yes	API name (case-sensitive)
`owner`	string	Yes	API owner (organization or user, case-sensitive)
`flatten`	boolean	—	Set to true to create models from inline schemas in OpenAPI definition (default false)
`version`	string	Yes	Version identifier
`resolved`	boolean	—	Set to true to get the resolved version with all external $refs included (default false)

Parameters from the server's own tool schema.

RISK

Why swagger_get_api_definition is rated Low

This tool retrieves API definitions from SwaggerHub Registry without modifying, executing against, or deleting any data. It is a straightforward query/fetch operation with no side effects. The parameters control the format and resolution of the returned definition (resolved refs, flattened models) but do not alter the stored definition itself.

From the tool's definition Tool description explicitly states 'Fetch resolved API definition' and parameters are all inputs (owner, api, version, resolved, flatten) with no indication of modification or deletion. The verb 'Fetch' is a read operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

swagger_get_api_definition Allowed

swagger_get_api_definition is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "swagger_get_api_definition": {}
  }
}

ALLOW ONLY 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_get_api_definition call is checked against it from then on.

FAQ

Questions about swagger_get_api_definition

What does the swagger_get_api_definition tool do? +

Fetch resolved API definition from SwaggerHub Registry based on owner, API name, and version. Parameters: - owner (string) *required*: API owner (organization or user, case-sensitive) - api (string) *required*: API name (case-sensitive) - version (string) *required*: Version identifier - resolved (boolean): Set to true to get the resolved version with all external $refs included (default false) - flatten (boolean): Set to true to create models from inline schemas in OpenAPI definition (default false). It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.

What parameters does swagger_get_api_definition accept? +

swagger_get_api_definition accepts 5 parameters: api, owner, flatten, version, resolved. Required: api, owner, version. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on swagger_get_api_definition? +

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

swagger_get_api_definition is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit swagger_get_api_definition? +

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

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

swagger_get_api_definition 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →