TMAegis

Explorateur de règles

Parcourez toutes les règles de durcissement du catalogue. Filtrez par plateforme, gravité, niveau de profil et selon que la vérification peut être automatisée.

55 règles trouvéessur 11 219Page 1 sur 3

IDTitreGravité
TMA-MCP-1.2Ensure server capability baseline is established and documentedmcp-server · Niveau 1Élevée
TMA-MCP-1.4Ensure MCP client and server identity metadata is captured and validated against the asset inventorymcp-server · Niveau 1Élevée
TMA-MCP-2.4Ensure required MCP request metadata headers are present and consistent with the request bodymcp-server · Niveau 1Élevée
TMA-MCP-2.5Ensure Origin header is validated on all Streamable HTTP requests to prevent DNS rebinding attacksmcp-server · Niveau 1Élevée
TMA-MCP-3.1.1Ensure stdio server credentials are sourced from the environment or OS credential storemcp-server · Niveau 1Élevée
TMA-MCP-3.1.2Ensure OIDC/OAuth 2.1 or short-lived API tokens are used for remote serversmcp-server · Niveau 1Élevée
TMA-MCP-3.2.3Ensure server-provided tool annotations are not relied upon for authorization or HITL gating decisionsmcp-server · Niveau 1Élevée
TMA-MCP-3.3.1Ensure OAuth tokens are audience-bound to the MCP server using Resource Indicatorsmcp-server · Niveau 1Élevée
TMA-MCP-4.1.3Ensure Elicitation requests are consented, redacted, and identity-boundmcp-server · Niveau 1Élevée
TMA-MCP-4.2.1Ensure filesystem scope is restricted to least privilege and enforced by OS-level controlsmcp-server · Niveau 1Élevée
TMA-MCP-4.2.3Ensure untrusted Resource URIs are not directly dereferenced outside MCP without scheme and destination policymcp-server · Niveau 1Élevée
TMA-MCP-4.3.1Ensure MCP Apps content is rendered in sandboxed isolation with Content Security Policy enforced from declared metadatamcp-server · Niveau 1Élevée
TMA-MCP-4.3.2Ensure MCP Apps permission requests default-deny, all app-to-host messages are logged, and high-risk channels are consentedmcp-server · Niveau 1Élevée
TMA-MCP-5.1.1Ensure tool schemas and argument types are validatedmcp-server · Niveau 1Élevée
TMA-MCP-5.1.2Ensure resource templates with explicit URI patterns and MIME types are usedmcp-server · Niveau 1Élevée
TMA-MCP-5.2.2Ensure sessions are not used as authentication and, where present, are bound to user identitymcp-server · Niveau 1Élevée
TMA-MCP-5.4.1Ensure path traversal and arbitrary filesystem access are preventedmcp-server · Niveau 1Élevée
TMA-MCP-6.1Ensure model context is minimized and MIME handling is honoredmcp-server · Niveau 1Élevée
TMA-MCP-6.3Ensure outbound proxy and DNS controls are applied for resource fetchersmcp-server · Niveau 1Élevée
TMA-MCP-7.1.1Ensure lifecycle and invocation metadata is recordedmcp-server · Niveau 1Élevée
TMA-MCP-7.1.2Ensure non-null JSON-RPC request IDs are enforced and included in audit logsmcp-server · Niveau 1Élevée
TMA-MCP-7.2.1Ensure alerts are generated on audience and issuer validation failuresmcp-server · Niveau 1Élevée
TMA-MCP-8.1Ensure third-party MCP servers and connectors are vetted and allowlists are enforcedmcp-server · Niveau 1Élevée
TMA-MCP-9.2Ensure the MCP server process is confined to its working set by OS-level kernel-enforced controlsmcp-server · Niveau 1Élevée
TMA-MCP-10.1Ensure safe, static resources are cached with freshness limits and per-user data is never shared-cachedmcp-server · Niveau 1Élevée