List all Lambda functions in the current region
AI agents call aws_list_lambda_functions to retrieve information from MCP Project Orchestrator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and queries existing Lambda function metadata without modifying, deleting, or executing any functions. It is purely informational, similar to other list operations on the server (aws_list_ec2_instances, aws_list_s3_buckets). The blast radius of misuse is minimal—an attacker could discover what Lambda functions exist in an AWS account, but cannot modify or execute them with this tool alone.
From the tool's definition Tool name and description indicate a list operation: 'List all Lambda functions in the current region'. This is a read-only query with no side effects.
Documented attack patterns abuse exactly the kind of access aws_list_lambda_functions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Project Orchestrator, and nothing reaches the server without passing your rules. This is the rule we recommend for aws_list_lambda_functions:
{
"version": "1",
"default": "deny",
"tools": {
"aws_list_lambda_functions": {}
}
} aws_list_lambda_functions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all Lambda functions in the current region. It is categorised as a Read tool in the MCP Project Orchestrator MCP Server, which means it retrieves data without modifying state.
Register the MCP Project Orchestrator MCP server in PolicyLayer and add a rule for aws_list_lambda_functions: 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 MCP Project Orchestrator. Nothing to install.
aws_list_lambda_functions 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 aws_list_lambda_functions 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 aws_list_lambda_functions. 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.
aws_list_lambda_functions is provided by the MCP Project Orchestrator MCP server (sparesparrow/mcp-project-orchestrator). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Project Orchestrator, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
15 MCP Project Orchestrator tools catalogued and risk-classified — across an index of 43,000+ MCP servers.