Aeon AI Risk Management
MCP security review checklist for tool-connected AI.
Aeon reviews MCP servers and tool-connected agents across inventory, permissions, command boundaries, authorization, secrets, logs, data paths, recovery, and Access / Execute / Leak risk before deployment.
Questions this page answers
- What should an MCP security review include?
- It should include server inventory, tool permissions, command boundaries, authorization, data paths, secrets handling, logging, recovery, and prompt/tool injection scenarios.
- Is this only for production systems?
- No. It is better to review MCP and tool-connected agents before production, but existing systems can also be tested and remediated.
- When does a checklist become a review?
- When the checklist shows real exposure or production risk, move into a signed CyberGuard scope with authorization, test windows, evidence handling, and retest rules.
Access checklist
List tools, roles, tenants, credentials, document stores, APIs, and object boundaries before testing who or what can reach them.
Execute checklist
Review command construction, parameter handling, workflow actions, prompt/tool injection, unsafe defaults, rollback behavior, and stop conditions.
Leak checklist
Review secrets, logs, retrieval outputs, file paths, error messages, response streams, and evidence handling so sensitive data does not escape.
Checklist first, signed testing second
Use the checklist to structure internal review. Active validation should move into a scoped CyberGuard engagement with written authorization and clear Rules of Engagement.