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