Skip to main content
Glama

list_web_acls

Retrieve Web ACLs for AWS WAF to monitor and manage security rules across CloudFront or regional applications.

Instructions

Lists Web ACLs (Global/CloudFront or Regional).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeNoThe scope of the Web ACLs (default: REGIONAL).

Implementation Reference

  • Handler function for 'list_web_acls' tool. Executes ListWebACLsCommand using WAFV2Client based on scope (REGIONAL or CLOUDFRONT), maps and returns Web ACL details.
    if (name === "list_web_acls") {
        const scope = (args as any)?.scope || "REGIONAL";
        const command = new ListWebACLsCommand({ Scope: scope });
        const response = await wafv2Client.send(command);
        const acls = response.WebACLs?.map(acl => ({
            Name: acl.Name,
            Id: acl.Id,
            ARN: acl.ARN,
            Description: acl.Description
        })) || [];
        return { content: [{ type: "text", text: JSON.stringify(acls, null, 2) }] };
  • src/index.ts:607-619 (registration)
    Registration of 'list_web_acls' tool in ListToolsResponse, including name, description, and input schema for scope.
        name: "list_web_acls",
        description: "Lists Web ACLs (Global/CloudFront or Regional).",
        inputSchema: {
            type: "object",
            properties: {
                scope: {
                    type: "string",
                    enum: ["CLOUDFRONT", "REGIONAL"],
                    description: "The scope of the Web ACLs (default: REGIONAL)."
                }
            }
        }
    },
  • Input schema for 'list_web_acls' tool defining optional 'scope' parameter.
    inputSchema: {
        type: "object",
        properties: {
            scope: {
                type: "string",
                enum: ["CLOUDFRONT", "REGIONAL"],
                description: "The scope of the Web ACLs (default: REGIONAL)."
            }
        }
    }
  • Initialization of WAFV2Client used by the list_web_acls handler.
    const wafv2Client = new WAFV2Client({});
  • Import of WAFV2Client and ListWebACLsCommand required for the tool.
    import { WAFV2Client, ListWebACLsCommand, GetSampledRequestsCommand, ListIPSetsCommand, GetIPSetCommand } from "@aws-sdk/client-wafv2";
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It states the action ('Lists') but lacks behavioral details such as pagination, rate limits, authentication requirements, or output format. This is a significant gap for a tool with no structured safety hints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero waste. It front-loads the core purpose and includes essential scope details, making it easy to parse without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits (e.g., read-only nature, error handling) and return values, which are critical for an agent to use the tool effectively in a cloud management context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with the parameter 'scope' fully documented in the schema (enum values and default). The description adds minimal value by mentioning 'Global/CloudFront or Regional', which aligns with the schema but doesn't provide additional semantics beyond it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Lists') and resource ('Web ACLs'), specifying the scope options (Global/CloudFront or Regional). It distinguishes the tool's focus on Web ACLs from siblings like list_cloudfront_distributions or list_security_groups, though it doesn't explicitly contrast with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. While it implies usage for listing Web ACLs, it doesn't mention prerequisites, context (e.g., AWS WAF setup), or compare to siblings like get_waf_sampled_requests, leaving the agent to infer appropriate scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bhaveshopss/MCP-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server