read_document

A read tool on the AWS MCP server.

SERVERAWS SOURCE@awslabs/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/aws/read-document.md

WHAT IT DOES

What read_document does on AWS

AI agents call read_document to retrieve information from AWS without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why read_document is rated Low

The tool name contains 'read', which typically indicates retrieval without side effects. Without a description, confidence is moderately reduced, but the semantic meaning of 'read_document' aligns with the Read category. In context of AWS and sibling tools involving policy attachment, service auditing, and user management, this tool likely retrieves document contents or metadata without modification.

From the tool's definition Tool name 'read_document' indicates data retrieval with no modification. Description is empty, but the name strongly suggests a read-only operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs read_document safely

PolicyLayer is an MCP gateway: it sits between your AI agents and AWS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For read_document, this is the rule to start with:

read_document Allowed

read_document is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "read_document": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect AWS, apply this rule, and every read_document call is checked against it from then on.

FAQ

Questions about read_document

What does the read_document tool do? +

read_document is a read tool on the AWS MCP server. It is categorised as a Read tool in the AWS MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on read_document? +

Register the AWS MCP server in PolicyLayer and add a rule for read_document: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches AWS. Nothing to install.

What risk level is read_document? +

read_document is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit read_document? +

Yes. Add a rate_limit block to the read_document rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block read_document completely? +

Set action: deny in the PolicyLayer policy for read_document. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides read_document? +

read_document is provided by the AWS MCP server (@awslabs/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on AWS, and thousands of servers like it.

This server

All 300 AWS tools →

Across the catalogue

read_input_file on 0gzk →claude_read_file on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →