search_documentation
AI agents call search_documentation to retrieve information from Amazon ElastiCache Memcached MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description, the tool name 'search_documentation' indicates a read-only operation that retrieves or queries documentation. This has no capability to modify, delete, or execute external operations. The lack of documentation decreases confidence slightly, but the semantic meaning of 'search' in this context aligns with Read category. Severity is low because accessing documentation poses minimal risk.
From the tool's definition Tool name 'search_documentation' combined with context of an ElastiCache Memcached MCP server. The name strongly implies documentation retrieval/querying with no side effects.
Attacks that exploit this kind of access
search_documentation. It is categorised as a Read tool in the Amazon ElastiCache Memcached MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Amazon ElastiCache Memcached MCP Server 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 Amazon ElastiCache Memcached MCP Server. Nothing to install.
search_documentation is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
search_documentation is provided by the Amazon ElastiCache Memcached MCP Server MCP server (awslabs.memcached-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.