search_cloudformation_documentation
AI agents call search_cloudformation_documentation to retrieve information from Awslabs Valkey without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'search_cloudformation_documentation' tool name strongly suggests a read-only operation that searches documentation—a retrieval operation with no side effects. No mutation, deletion, execution, or financial implications are evident from the name. However, confidence is moderate (0.6) due to the empty description providing no direct verification of the tool's actual behavior or scope.
From the tool's definition Tool name contains 'search' which indicates querying/retrieval. Description is empty, limiting evidence assessment.
Attacks that exploit this kind of access
search_cloudformation_documentation. It is categorised as a Read tool in the Awslabs Valkey MCP Server, which means it retrieves data without modifying state.
Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for search_cloudformation_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 Awslabs Valkey. Nothing to install.
search_cloudformation_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_cloudformation_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_cloudformation_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_cloudformation_documentation is provided by the Awslabs Valkey MCP server (awslabs.valkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.