---
title: Tip: don't auto-approve MCP tools just because they say 'read-only', and rotate any token an MCP server held while it could be steered to a new URL | ctxsec
url: https://ctxsec.com/items/tip-remove-read-only-annotated-mcp-tools-from-auto-approve-and-rotate-tokens-after-aws-mcp-fixes
description: "AWS's two MCP fixes show the two common failures: a server that connects wherever the model tells it, and a tool whose self-declared annotation was wrong."
status: "guide (based on AWS Security Bulletins 2026-184-AWS and 2026-185-AWS)"
published: 2026-11-20
---

> AWS's two MCP fixes show the two common failures: a server that connects wherever the model tells it, and a tool whose self-declared annotation was wrong.

[← Tips & Guides](/tips) · [markdown](/items/tip-remove-read-only-annotated-mcp-tools-from-auto-approve-and-rotate-tokens-after-aws-mcp-fixes.md)

guide (based on AWS Security Bulletins 2026-184-AWS and 2026-185-AWS)

2026-11-20 3:49 PM ET

### Tip: don't auto-approve MCP tools just because they say 'read-only', and rotate any token an MCP server held while it could be steered to a new URL

- Review your MCP client's auto-approve list; include only tools you've verified are truly read-only.
- Give MCP servers least-privilege tokens scoped to one database or bucket, and rotate tokens after any endpoint-steering bug.
- Where possible, pin MCP server connection targets in config rather than letting tool arguments set them.

Sources: [AWS Security Bulletin 2026-184-AWS: CVE-2026-126816, path traversal and arbitrary file write in aws-pricing-mcp-server (Nov 16, 2026)](https://aws.amazon.com/security/security-bulletins/2026-184-aws/) · [AWS Security Bulletin 2026-185-AWS: CVE-2026-126681, improper restriction of endpoints in Timestream for InfluxDB MCP Server (Nov 16, 2026)](https://aws.amazon.com/security/security-bulletins/2026-185-aws/)
