get_lambda_event_schemas
AI agents call get_lambda_event_schemas 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.
This tool retrieves Lambda event schemas—metadata or configuration information—without creating, modifying, deleting, or executing code. The 'get_' prefix is characteristic of Read category tools. The empty description reduces confidence slightly, but the semantic intent is clear. No side effects or irreversible operations are suggested.
From the tool's definition Tool name 'get_lambda_event_schemas' contains 'get', which indicates retrieval of data with no modification.
Attacks that exploit this kind of access
get_lambda_event_schemas. 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 get_lambda_event_schemas: 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.
get_lambda_event_schemas 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 get_lambda_event_schemas 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 get_lambda_event_schemas. 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.
get_lambda_event_schemas 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.