MCP security checklist: observe
Six steps keep a record and watch for change: log every tool call with parameters, redact secrets, alert on changed tool definitions, alert on new servers and destinations, forward logs to the SIEM and track advisories for approved components. Each step has controls and sources and a priority from the written rule, read on 16 Nov 2026.
Facts read on .
What this stage covers
Record and watch tool calls and changes. There are 6 steps here (C-31 to C-36), each a concrete action an engineer can tick.
Sources: OWASP MCP Security Cheat Sheet; MCP Security Best Practices, 2026-07-28 revision; MCP Tools, 2026-07-28 revision.
Steps in order
Do these in order; each step lists how to do it and the register risks it closes.
- C-31 Log every tool call with its parameters (priority medium)
- C-32 Redact secrets and personal data in logs (priority medium)
- C-33 Alert when tool definitions change (priority medium)
- C-34 Alert on new servers, destinations and cross-server data flows (priority high)
- C-35 Send MCP logs to the SIEM (priority medium)
- C-36 Track advisories for approved components (priority medium)
Sources: OWASP MCP Security Cheat Sheet; MCP Security Best Practices, 2026-07-28 revision; MCP Tools, 2026-07-28 revision; Evo ADS MCP Governance Goes GA, Snyk.
Where the settings come from
Setting names appear only where a primary source documents them. Check each against the client version in use before rollout, because the 2026-07-28 MCP revision and client releases changed several defaults.
Sources: OWASP MCP Security Cheat Sheet; MCP Security Best Practices, 2026-07-28 revision; MCP Tools, 2026-07-28 revision; Evo ADS MCP Governance Goes GA, Snyk.
Observe: 6 items
C-31: Log every tool call with its parameters
Record the tool, parameters, user and time for each invocation.
Impact: Without records an incident cannot be reconstructed.
Controls:
- Capture the same fields for every client.
- Keep the logs long enough for your investigation window.
- Register risks: R-40.
Severity: medium
Sources: OWASP MCP Security Cheat Sheet (read ); MCP Security Best Practices, 2026-07-28 revision (read ).
C-32: Redact secrets and personal data in logs
Mask credentials and personal data in parameters and results before they are stored.
Impact: Logs otherwise become a second store of secrets.
Controls:
- Test redaction with sample credentials.
- Restrict log access and set retention.
- Register risks: R-41.
Severity: medium
Sources: OWASP MCP Security Cheat Sheet (read ).
C-33: Alert when tool definitions change
Compare tool definitions with the pinned hash and alert on any difference, including annotation changes.
Impact: A changed definition is the signal of a rug pull.
Controls:
- Re-prompt for consent on change.
- Alert on listChanged notifications from servers not expected to change.
- Register risks: R-05, R-26.
Severity: medium
Sources: OWASP MCP Security Cheat Sheet (read ); MCP Tools, 2026-07-28 revision (read ).
C-34: Alert on new servers, destinations and cross-server data flows
Watch for unapproved servers appearing, new outbound hosts and one server's values showing up in another's calls.
Impact: These patterns mark shadowing, exfiltration and unknown installs.
Controls:
- Add detections for new tools called, unusual call rates and admin-level queries.
- Feed alerts to the same queue as other security alerts.
- Register risks: R-24, R-38, R-22, R-07.
Severity: high
Sources: OWASP MCP Security Cheat Sheet (read ); Evo ADS MCP Governance Goes GA, Snyk (read ).
C-35: Send MCP logs to the SIEM
Forward tool-call logs to the system your responders already use.
Impact: Detection only works if the logs reach the people who can act.
Controls:
- Use a common schema across clients.
- Map fields to user and device identity.
- Register risks: R-40.
Severity: medium
Sources: OWASP MCP Security Cheat Sheet (read ).
C-36: Track advisories for approved components
Subscribe to GitHub advisories and release notes for every server and SDK in the catalog.
Impact: Fixes such as the October 2026 SDK advisories only matter if someone reads them.
Controls:
- Map each advisory to catalog entries and owners.
- Record the date the fix was deployed.
- Register risks: R-04, R-13.
Severity: medium
Sources: GHSA-rvq5-wwqv-78pq: MCP TypeScript SDK bearer authentication audience (read ); MCP Python SDK v2.2.0 release notes (read ).