MyVaultDesk
Find the resource with the right context.
Resource names alone are not enough. Use the vault, project, environment and version to identify what your task requires.
What belongs in a vault
| Resource | Useful context |
|---|---|
| API key | Application, provider and environment |
| Connection information | Service, endpoint and environment |
| Certificate | Associated service, version and expiration |
| Shared credential | Owner, intended use and access scope |
Discover, then consult
Start by identifying the resource available to your connection. Check its context before requesting content. MCP resources have identifiers; use the identifier returned by the service rather than inventing a path or guessing a name.
Find the gateway certificate for the platform project in staging. Summarize its version and expiration information. Do not include private key material.PROMPT
Versions and expiration
A previous resource version provides historical context; it is not necessarily valid for current use. Check the version and expiration information before using a certificate or credential. Follow your team's renewal process when a resource needs attention.