portkey-admin-mcp 0.11.0 → 0.11.1

package/ENDPOINTS.md

@@ -1,7 +1,7 @@
 # Portkey Admin API endpoints and MCP tools
 
 Generated from the registered tool catalog by `npm run generate:endpoints`.
-Route mappings were reviewed against the official Portkey OpenAPI on 2026-08-27.
+Route mappings were reviewed against the official Portkey OpenAPI on 2026-08-28.
 
 - Base URL: `https://api.portkey.ai/v1`
 - Authentication: `x-portkey-api-key`
@@ -139,7 +139,7 @@ Routes:
 | `list_virtual_keys` | List provider API keys stored as virtual keys in your Portkey org. Use this to find slugs before wiring prompts/configs or auditing limits. Returns total plus name, slug, status, usage limits, rate limits, reset state, and model config. |
 | `create_virtual_key` | Store a provider API key as a virtual key. The raw key is encrypted and only returned at creation time, so save the returned slug and use it in prompts/configs. Optional usage and rate limits apply immediately, and the tool returns the new slug. |
 | `get_virtual_key` | Fetch one virtual key by slug, including metadata, a masked secret, limits, status, and model config. Use this before updating or to inspect the current configuration. |
-| `update_virtual_key` | Update a virtual key's name, secret, note, or limits. Rotating the key takes effect immediately, and limit changes apply to downstream prompts and configs using this slug. Returns the updated name, slug, and status. |
+| `update_virtual_key` | Update a virtual key's name, secret, note, or limits. Rotating the key takes effect immediately, and limit changes apply to downstream prompts and configs using this slug. Returns success when Portkey accepts the update. |
 | `delete_virtual_key` | Delete a virtual key by slug. This is irreversible and will break prompts and configs that reference the slug, so confirm no active dependencies first. Returns success after removal. |
 | `create_api_key` | Create a Portkey API key for auth. Org keys grant broader access; workspace keys are scoped. WARNING: The key secret is returned ONCE in the tool result and will be visible in MCP transcripts and LLM context — store it securely immediately. Using the key grants access immediately according to its scopes, defaults, and limits. Workspace keys require workspace_id and user keys require user_id. |
 | `list_api_keys` | List Portkey API keys for auditing access, scopes, defaults, limits, and expiration. Use this for API keys only; use list_virtual_keys for provider keys. Returns total plus id, type, status, workspace/user scope, limits, defaults, alert emails, and creation mode. |

package/docs/PRISMA_AIRS_INTEROPERABILITY.md

@@ -1,6 +1,6 @@
 # Prisma AIRS interoperability
 
-Last verified: 2026-08-27
+Last verified: 2026-08-28
 
 ## Short answer
 
@@ -19,6 +19,10 @@ Changing `PORTKEY_BASE_URL` to a Prisma AIRS or Strata Cloud Manager URL will no
 
 Palo Alto Networks says the Portkey acquisition makes Portkey the core AI Gateway for Prisma AIRS. Its current AI Gateway instructions direct administrators to Strata Cloud Manager, while the documented Prisma AIRS MCP endpoint is for centralized AI-agent security. No public Prisma AIRS admin contract equivalent to Portkey's users, workspaces, prompts, configs, integrations, or keys is documented today. That last sentence is an inference from the currently published product and API documentation, not a promise that such an API will never exist.
 
+The August 2026 Prisma AIRS additions cover runtime, model, skill, discovery, and
+red-team security capabilities. They do not publish a Portkey-compatible AI
+Gateway administration contract, so they do not change this boundary.
+
 ## Recommended coexistence
 
 Run the two MCP servers side by side when you need both administration and runtime security:

package/package.json

@@ -56,7 +56,7 @@
 	},
 	"name": "portkey-admin-mcp",
 	"mcpName": "io.github.CodesWhat/portkey-admin-mcp",
-	"version": "0.11.0",
+	"version": "0.11.1",
 	"main": "build/index.js",
 	"keywords": [
 		"mcp",