swagger_standardize_api
Standardize and fix an API definition using AI to ensure compliance with governance policies. Scans the API definition for standardization errors and automatically fixes them using SmartBear AI. Optionally provide 'newVersion' (e.g. patch bump '1.0.0' → '1.0.1') to save the fixed definition as a ...
This record as markdown: /tools/smartbear-mcp/swagger-standardize-api.md
What swagger_standardize_api does on SmartBear MCP
AI agents use swagger_standardize_api 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 |
|---|---|---|---|
api | string | Yes | API name (case-sensitive) |
owner | string | Yes | API owner (organization or user, case-sensitive) |
version | string | Yes | Version identifier |
newVersion | string | — | The version to save the fixed definition as (e.g. '1.0.1'). Omitting this will overwrite the current version — prefer providing a patch bump (e.g. '1.0.0' → '1. |
Parameters from the server's own tool schema.
Why swagger_standardize_api is rated Medium
This tool modifies API definitions by applying standardization fixes. While it could theoretically create a new version (reversible), the default behavior is to overwrite the current version, and even version creation represents persistent modification of governance artifacts.
From the tool's definition "automatically fixes them" and "will overwrite the current version" and "save the fixed definition as a new version" indicate the tool modifies API definitions.
Attacks that exploit this kind of access
The rule that runs swagger_standardize_api 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_standardize_api, this is the rule to start with:
swagger_standardize_api 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.
The button opens the PolicyLayer dashboard: create your workspace, connect SmartBear MCP, apply this rule, and every swagger_standardize_api call is checked against it from then on.
Questions about swagger_standardize_api
Standardize and fix an API definition using AI to ensure compliance with governance policies. Scans the API definition for standardization errors and automatically fixes them using SmartBear AI. Optionally provide 'newVersion' (e.g. patch bump '1.0.0' → '1.0.1') to save the fixed definition as a new version — omitting it will overwrite the current version. Returns the number of errors found and the fixed definition if successful. Use this tool when users ask to standardize, fix, govern, or ensure governance compliance of APIs. Parameters: - owner (string) *required*: API owner (organization or user, case-sensitive) - api (string) *required*: API name (case-sensitive) - version (string) *required*: Version identifier - newVersion (string): The version to save the fixed definition as (e.g. '1.0.1'). Omitting this will overwrite the current version — prefer providing a patch bump (e.g. '1.0.0' → '1.0.1') unless the user specifies otherwise. 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.
swagger_standardize_api accepts 4 parameters: api, owner, version, newVersion. Required: api, owner, version. 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_standardize_api: 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_standardize_api is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the swagger_standardize_api 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_standardize_api. 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_standardize_api 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