Returns AWS Lambda event schemas for different event sources (e.g. s3, sns, apigw) and programming languages. When a event source triggers a Lambda function, the request payload comes in a specific format. Each Lambda event source defines its own schema and language-specific types, which should ...
Single-target operation
Part of the AWS Serverless MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call get_lambda_event_schemas to retrieve information from AWS Serverless MCP Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_lambda_event_schemas only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
get_lambda_event_schemas:
rules:
- action: allowSee the full AWS Serverless MCP Server policy for all 32 tools.
Agents calling read-class tools like get_lambda_event_schemas have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Returns AWS Lambda event schemas for different event sources (e.g. s3, sns, apigw) and programming languages. When a event source triggers a Lambda function, the request payload comes in a specific format. Each Lambda event source defines its own schema and language-specific types, which should be used in the Lambda function handler to correctly parse the event data. If you cannot find a schema for your event source, you can directly parse the event data as a JSON object. For EventBridge events, you must use the list_registries, search_schema, and describe_schema tools to access the schema registry directly, get schema definitions, and generate code processing logic. Returns: Dict: Lambda event schema source code file for the request runtime and event source. It is categorised as a Read tool in the AWS Serverless MCP Server MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for get_lambda_event_schemas. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AWS Serverless MCP Server MCP server.
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 Intercept 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 Intercept 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 AWS Serverless MCP Server MCP server (awslabs.aws-serverless-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.