Demo data. Example Corp is fictitious, and nothing you do here is saved.
Example Corp assistant
Start a reviewMCP server with 6 tools and 11 API operations. No approved baseline yet.
8 of 46 findings
Warnings2
| Finding | Who acts |
|---|---|
reportsThe scope has no real descriptionScopeNeat recommendation: Write one plain sentence saying what the scope allows, and on which data.Next step: The steward writes what the scope allows, and the resource owner confirms it before approving the scope.Sources: OpenAPI 3.1.1 §4.8.29.1. YogaSec practiceReferences (2)A finding supports evidence for these requirements. On its own it does not make an organization compliant.
| Accountable: Resource ownerResponsible: Scope stewardInformed: Internal audit |
process_refundThe tool can both start an action and approve itOperations: createRefund, approveRefundScopeNeat recommendation: Split the tool in two, and leave approving to another client or to a person. Or give approving the human approval mode.Next step: The MCP server owner splits the tool, security is consulted on who approves, and the resource owner approves the new mapping.Sources: NIST SP 800-53 AC-5. YogaSec practiceReferences (2)A finding supports evidence for these requirements. On its own it does not make an organization compliant.
| Accountable: Resource ownerResponsible: MCP server ownerConsulted: SecurityInformed: Internal audit |
Notes6
| Finding | Who acts |
|---|---|
read_usersDeclared but used by nothing hereScopeNeat recommendation: Find who still requests it. If nobody does, remove it from the authorization server and from the API description.Next step: The resource owner confirms retirement, and IAM engineering removes it after checking that no client still requests it.Sources: RFC 6749 §3.3. YogaSec practiceReferences (2)A finding supports evidence for these requirements. On its own it does not make an organization compliant.
| Accountable: Resource ownerResponsible: Scope stewardResponsible: IAM engineeringConsulted: Client software ownerInformed: Internal audit |
getUsersDeclared but used by nothing hereScopeNeat recommendation: Find who still requests it. If nobody does, remove it from the authorization server and from the API description.Next step: The resource owner confirms retirement, and IAM engineering removes it after checking that no client still requests it.Sources: RFC 6749 §3.3. YogaSec practiceReferences (2)A finding supports evidence for these requirements. On its own it does not make an organization compliant.
| Accountable: Resource ownerResponsible: Scope stewardResponsible: IAM engineeringConsulted: Client software ownerInformed: Internal audit |
User.ReadDeclared but used by nothing hereScopeNeat recommendation: Find who still requests it. If nobody does, remove it from the authorization server and from the API description.Next step: The resource owner confirms retirement, and IAM engineering removes it after checking that no client still requests it.Sources: RFC 6749 §3.3. YogaSec practiceReferences (2)A finding supports evidence for these requirements. On its own it does not make an organization compliant.
| Accountable: Resource ownerResponsible: Scope stewardResponsible: IAM engineeringConsulted: Client software ownerInformed: Internal audit |
user.readDeclared but used by nothing hereScopeNeat recommendation: Find who still requests it. If nobody does, remove it from the authorization server and from the API description.Next step: The resource owner confirms retirement, and IAM engineering removes it after checking that no client still requests it.Sources: RFC 6749 §3.3. YogaSec practiceReferences (2)A finding supports evidence for these requirements. On its own it does not make an organization compliant.
| Accountable: Resource ownerResponsible: Scope stewardResponsible: IAM engineeringConsulted: Client software ownerInformed: Internal audit |
api:writeDeclared but used by nothing hereScopeNeat recommendation: Find who still requests it. If nobody does, remove it from the authorization server and from the API description.Next step: The resource owner confirms retirement, and IAM engineering removes it after checking that no client still requests it.Sources: RFC 6749 §3.3. YogaSec practiceReferences (2)A finding supports evidence for these requirements. On its own it does not make an organization compliant.
| Accountable: Resource ownerResponsible: Scope stewardResponsible: IAM engineeringConsulted: Client software ownerInformed: Internal audit |
factures:créerDeclared but used by nothing hereScopeNeat recommendation: Find who still requests it. If nobody does, remove it from the authorization server and from the API description.Next step: The resource owner confirms retirement, and IAM engineering removes it after checking that no client still requests it.Sources: RFC 6749 §3.3. YogaSec practiceReferences (2)A finding supports evidence for these requirements. On its own it does not make an organization compliant.
| Accountable: Resource ownerResponsible: Scope stewardResponsible: IAM engineeringConsulted: Client software ownerInformed: Internal audit |