openapi-specification-v2
Audited by Runlayer on Feb 21, 2026
Malicious tool definition detected
Tool: SKILL.md Description: --- name: openapi-specification-v2 description: OpenAPI (Swagger) 2.0 specification for describing REST APIs.
Malicious tool definition detected
| Field | Type | Description | |-----------|---------|-------------| | name | string | Element/attribute name override. For array items: name of each element; for array with wrapped: true, name of wrapper. | | namespace | string | Namespace URL. | | prefix | string | Namespace prefix. | | attribute | boolean | true = render as attribute; default false. | | wrapped | boolean | For arrays only: true = wrapped element (e.g. <books><book/><book/></books>);
Malicious tool definition detected
Tool: references/advanced-security-filtering.md Description: --- name: advanced-security-filtering description: Security filtering and empty Paths/Path Item in Swagger 2.0 --- # Security Filtering Some objects in the Swagger spec may be **empty** or **removed** for access control over the documentation itself.
Malicious tool definition detected
Tool: references/advanced-vendor-extensions.md Description: --- name: advanced-vendor-extensions description: Vendor extensions (x-) in Swagger 2.0 --- # Vendor Extensions (x-) Extensions allow additional data at certain points in the spec.
Malicious tool definition detected
- Use operationId + tags + clear responses so codegen and docs stay predictable. <!-- Source references: - https://github.com/OAI/OpenAPI-Specification/blob/main/versions/2.0.md -->
Malicious tool definition detected
Tool: references/core-data-types-and-formats.md Description: --- name: core-data-types-and-formats description: Primitive data types, format modifiers, and validation in Swagger 2.0 --- # Data Types and Formats Types are based on **JSON Schema Draft 4**.
Malicious tool definition detected
Tool: references/core-example-object.md Description: --- name: core-example-object description: Example Object for response examples by MIME type in Swagger 2.0 --- # Example Object Allows sharing **examples** for operation responses.
Malicious tool definition detected
Tool: references/core-fixed-patterned-fields.md Description: --- name: core-fixed-patterned-fields description: Fixed fields vs patterned fields in Swagger 2.0 --- # Fixed and Patterned Fields The Swagger schema exposes two kinds of fields. This affects how you add or extend content.
Malicious tool definition detected
Tool: references/core-format-and-structure.md Description: --- name: core-format-and-structure description: OpenAPI/Swagger 2.0 document format, file structure, and data types --- # Format and Structure (Swagger 2.0) Swagger 2.0 specs are JSON or YAML.
Malicious tool definition detected
Tool: references/core-header-object.md Description: --- name: core-header-object description: Header Object for response headers in Swagger 2.0 --- # Header Object Describes a single response header.
Malicious tool definition detected
Tool: references/core-headers-object.md Description: --- name: core-headers-object description: Headers Object container for response headers in Swagger 2.0 --- # Headers Object A **container** for the headers that can be sent as part of a response.
Malicious tool definition detected
Tool: references/core-http-status-codes.md Description: --- name: core-http-status-codes description: HTTP status codes as response keys and default response in Swagger 2.0 --- # HTTP Status Codes Response keys in the [Responses Object](responses.md) are HTTP status codes.
Malicious tool definition detected
Tool: references/core-info-metadata.md Description: --- name: core-info-metadata description: Info, Contact, License, and API metadata in Swagger 2.0 --- # Info and Metadata Objects ## Info Object Required at root.
Malicious tool definition detected
Tool: references/core-items-object.md Description: --- name: core-items-object description: Items Object for non-body array parameters and header arrays in Swagger 2.0 --- # Items Object A **limited subset** of JSON Schema's items object.
Malicious tool definition detected
Tool: references/core-mime-types.md Description: --- name: core-mime-types description: MIME types for consumes and produces in Swagger 2.0 --- # MIME Types MIME type definitions for `consumes` (request body) and `produces` (response body) MUST comply with [RFC 6838](http://tools.ietf.org/html/rfc6838).
Malicious tool definition detected
Tool: references/core-path-templating.md Description: --- name: core-path-templating description: Path templating and path parameters in Swagger 2.0 --- # Path Templating Path templating uses **curly braces `{}`** to mark a section of the URL path as replaceable by a [path parameter](parameters.md).
Malicious tool definition detected
Tool: references/core-reference-object.md Description: --- name: core-reference-object description: Reference Object ($ref), JSON Pointer, and multi-file references in Swagger 2.0 --- # Reference Object Allows referencing other definitions in the spec.
Malicious tool definition detected
Tool: references/core-swagger-object.md Description: --- name: core-swagger-object description: Root Swagger object and required/optional fields for OpenAPI 2.0 --- # Swagger Object (Root) Root of the API spec.
Malicious tool definition detected
Tool: references/core-tags-and-external-docs.md Description: --- name: core-tags-and-external-docs description: Tag Object and External Documentation Object in Swagger 2.0 --- # Tags and External Documentation ## Tag Object At root under `tags`.
Malicious tool definition detected
Tool: references/parameters-collection-format.md Description: --- name: parameters-collection-format description: collectionFormat for array parameters and items in Swagger 2.0 --- # collectionFormat Determines how **array** values are serialized for parameters (and for [Items Object](core-items-object.md) in parameters/headers).
Malicious tool definition detected
Tool: references/parameters-definitions-reuse.md Description: --- name: parameters-definitions-reuse description: Root-level Parameters Definitions Object and reusing parameters via $ref in Swagger 2.0 --- # Parameters Definitions (Reuse) The root **parameters** object holds reusable parameter definitions.
Malicious tool definition detected
Tool: references/parameters.md Description: --- name: parameters description: Parameter Object, locations, body vs non-body, and Items Object in Swagger 2.0 --- # Parameters A parameter is uniquely identified by **name** + **in** (location). At most **one body** parameter per operation.
Malicious tool definition detected
Tool: references/path-item-ref.md Description: --- name: path-item-ref description: Path Item $ref and external path definition in Swagger 2.0 --- # Path Item $ref A [Path Item Object](paths-and-operations.md) can be defined **externally** using the `$ref` field.
Malicious tool definition detected
Tool: references/paths-and-operations.md Description: --- name: paths-and-operations description: Paths Object, Path Item, and Operation Object in Swagger 2.0 --- # Paths and Operations ## Paths Object Maps relative path strings to Path Item objects. Path is appended to `basePath` to form the full URL. Path keys MUST start with `/`.
Malicious tool definition detected
Tool: references/responses-definitions-reuse.md Description: --- name: responses-definitions-reuse description: Root-level Responses Definitions Object and reusing responses via $ref in Swagger 2.0 --- # Responses Definitions (Reuse) The root **responses** object holds reusable response definitions.
Malicious tool definition detected
Tool: references/responses.md Description: --- name: responses description: Responses Object, Response Object, Headers, and Example in Swagger 2.0 --- # Responses ## Responses Object (operation level) Maps HTTP status codes (and `default`) to response definitions.
Malicious tool definition detected
Tool: references/schema-and-definitions.md Description: --- name: schema-and-definitions description: Schema Object, Definitions, Reference, composition and polymorphism in Swagger 2.0 --- # Schema and Definitions ## Schema Object Based on **JSON Schema Draft 4** subset. Used for body parameters, response bodies, and `definitions`.
Malicious tool definition detected
Tool: references/schema-json-schema-keywords.md Description: --- name: schema-json-schema-keywords description: JSON Schema subset supported in Schema Object in Swagger 2.0 --- # Schema Object — JSON Schema Subset The [Schema Object](schema-and-definitions.md) is based on **JSON Schema Draft 4** and uses a predefined subset.
Malicious tool definition detected
Tool: references/security-basic-apikey.md Description: --- name: security-basic-apikey description: basic and apiKey Security Scheme in Swagger 2.0 --- # Basic and API Key Security Schemes When [Security Scheme Object](security.md) `type` is `basic` or `apiKey`, use the fields below.
Malicious tool definition detected
Tool: references/security-oauth2-flows.md Description: --- name: security-oauth2-flows description: OAuth2 security scheme flows and required URLs in Swagger 2.0 --- # OAuth2 Flows (Security Scheme) When `type` is `oauth2`, the Security Scheme Object must include `flow` and the URLs required for that flow.
Malicious tool definition detected
Tool: references/security-requirement-object.md Description: --- name: security-requirement-object description: Security Requirement Object for applying security to API or operations in Swagger 2.0 --- # Security Requirement Object Declares which **security schemes** are required to execute the API (at root) or an operation (per operation).
Malicious tool definition detected
Tool: references/security-scopes-object.md Description: --- name: security-scopes-object description: Scopes Object for OAuth2 security scheme in Swagger 2.0 --- # Scopes Object Lists the **available scopes** for an OAuth2 [Security Scheme](security.md).
Malicious tool definition detected
Tool: references/security.md Description: --- name: security description: Security Definitions, Security Scheme, Security Requirement, and Scopes in Swagger 2.0 --- # Security ## Security Definitions Object At root: `securityDefinitions`. Maps scheme name → Security Scheme Object.
Tool passed security scan