search_documentation

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/search-documentation.md

WHAT IT DOES

What search_documentation does on AWS

AI agents call search_documentation 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 search_documentation is rated Low

Based on the tool name alone, searching documentation is a retrieval operation with no side effects. The empty description reduces confidence slightly, but the name strongly suggests a Read category action. No sibling tools provide additional context about this specific tool's actual implementation.

From the tool's definition Tool named 'search_documentation' with no description provided. The name indicates a read-only operation that queries/searches documentation content.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search_documentation 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 search_documentation, this is the rule to start with:

search_documentation Allowed

search_documentation 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": {
    "search_documentation": {}
  }
}

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 search_documentation call is checked against it from then on.

FAQ

Questions about search_documentation

What does the search_documentation tool do? +

search_documentation 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 search_documentation? +

Register the AWS MCP server in PolicyLayer and add a rule for search_documentation: 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 search_documentation? +

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

Can I rate-limit search_documentation? +

Yes. Add a rate_limit block to the search_documentation 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 search_documentation completely? +

Set action: deny in the PolicyLayer policy for search_documentation. 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 search_documentation? +

search_documentation 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

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

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