Skip to main content
Glama
purpleax

Fastly NGWAF MCP Server

by purpleax

manage_cloudwaf

Manage Fastly CloudWAF instances to protect web applications by listing, creating, updating, or deleting deployments with configuration options for domains, regions, and security settings.

Instructions

Manage CloudWAF instances

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
corpNameNoCorporation name (uses context default if not provided)
actionYesAction to perform
deploymentIdNoDeployment ID (for get/update/delete)
nameNoInstance name
descriptionNoInstance description
regionNoAWS region
tlsMinVersionNoMinimum TLS version
siteNameNoSite name for configuration
domainsNoDomains to protect
originNoOrigin server URL

Implementation Reference

  • Primary execution handler for the 'manage_cloudwaf' tool. Dispatches to appropriate CloudWAF client methods based on the 'action' parameter (list, create, get, update, delete).
    case 'manage_cloudwaf':
        const { corpName: corpForCloudWAF } = resolveContext(typedArgs);
        if (typedArgs.action === 'list') {
            result = await client.listCloudWAFInstances(corpForCloudWAF);
        }
        else if (typedArgs.action === 'create') {
            const instanceData = {
                name: typedArgs.name,
                description: typedArgs.description,
                region: typedArgs.region,
                tlsMinVersion: typedArgs.tlsMinVersion,
                workspaceConfigs: [{
                        siteName: typedArgs.siteName,
                        instanceLocation: "direct",
                        listenerProtocols: ["https"],
                        routes: [{
                                domains: typedArgs.domains,
                                origin: typedArgs.origin,
                                passHostHeader: false,
                                connectionPooling: true,
                                trustProxyHeaders: false,
                            }],
                    }],
            };
            result = await client.createCloudWAFInstance(corpForCloudWAF, instanceData);
        }
        else if (typedArgs.action === 'get') {
            result = await client.getCloudWAFInstance(corpForCloudWAF, typedArgs.deploymentId);
        }
        else if (typedArgs.action === 'update') {
            const instanceData = {
                name: typedArgs.name,
                description: typedArgs.description,
                region: typedArgs.region,
                tlsMinVersion: typedArgs.tlsMinVersion,
            };
            result = await client.updateCloudWAFInstance(corpForCloudWAF, typedArgs.deploymentId, instanceData);
        }
        else if (typedArgs.action === 'delete') {
            result = await client.deleteCloudWAFInstance(corpForCloudWAF, typedArgs.deploymentId);
        }
        break;
  • server.js:777-796 (registration)
    Registration of the 'manage_cloudwaf' tool in the tools list, including name, description, and input schema. This is returned by the ListToolsRequestSchema handler.
    {
        name: 'manage_cloudwaf',
        description: 'Manage CloudWAF instances',
        inputSchema: {
            type: 'object',
            properties: {
                corpName: { type: 'string', description: 'Corporation name (uses context default if not provided)' },
                action: { type: 'string', enum: ['list', 'create', 'get', 'update', 'delete'], description: 'Action to perform' },
                deploymentId: { type: 'string', description: 'Deployment ID (for get/update/delete)' },
                name: { type: 'string', description: 'Instance name' },
                description: { type: 'string', description: 'Instance description' },
                region: { type: 'string', description: 'AWS region' },
                tlsMinVersion: { type: 'string', enum: ['1.0', '1.2'], description: 'Minimum TLS version' },
                siteName: { type: 'string', description: 'Site name for configuration' },
                domains: { type: 'array', items: { type: 'string' }, description: 'Domains to protect' },
                origin: { type: 'string', description: 'Origin server URL' },
            },
            required: ['action'],
        },
    },
  • Input schema definition for the 'manage_cloudwaf' tool, specifying parameters and validation rules.
    inputSchema: {
        type: 'object',
        properties: {
            corpName: { type: 'string', description: 'Corporation name (uses context default if not provided)' },
            action: { type: 'string', enum: ['list', 'create', 'get', 'update', 'delete'], description: 'Action to perform' },
            deploymentId: { type: 'string', description: 'Deployment ID (for get/update/delete)' },
            name: { type: 'string', description: 'Instance name' },
            description: { type: 'string', description: 'Instance description' },
            region: { type: 'string', description: 'AWS region' },
            tlsMinVersion: { type: 'string', enum: ['1.0', '1.2'], description: 'Minimum TLS version' },
            siteName: { type: 'string', description: 'Site name for configuration' },
            domains: { type: 'array', items: { type: 'string' }, description: 'Domains to protect' },
            origin: { type: 'string', description: 'Origin server URL' },
        },
        required: ['action'],
  • Supporting methods in the FastlyNGWAFClient class that implement the core API interactions for managing CloudWAF instances (list, create, get, update, delete).
    // CloudWAF Management
    async listCloudWAFInstances(corpName) {
        const response = await this.api.get(`/corps/${corpName}/cloudwafInstances`);
        return response.data;
    }
    async createCloudWAFInstance(corpName, instanceData) {
        const response = await this.api.post(`/corps/${corpName}/cloudwafInstances`, instanceData);
        return response.data;
    }
    async getCloudWAFInstance(corpName, deploymentId) {
        const response = await this.api.get(`/corps/${corpName}/cloudwafInstances/${deploymentId}`);
        return response.data;
    }
    async updateCloudWAFInstance(corpName, deploymentId, instanceData) {
        const response = await this.api.put(`/corps/${corpName}/cloudwafInstances/${deploymentId}`, instanceData);
        return response.data;
    }
    async deleteCloudWAFInstance(corpName, deploymentId) {
        await this.api.delete(`/corps/${corpName}/cloudwafInstances/${deploymentId}`);
        return { success: true };
    }
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails completely. 'Manage' could imply any combination of create, read, update, or delete operations, but the description doesn't clarify which actions are supported, what permissions are required, whether operations are destructive, what happens on success/failure, or any rate limits. For a tool with 10 parameters that appears to handle potentially destructive operations (delete action), this lack of transparency is critical.

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 maximally concise at just three words. While this conciseness comes at the expense of usefulness, it's not verbose or poorly structured. Every word technically earns its place, though collectively they provide minimal value. The description is front-loaded with its only content.

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

Completeness1/5

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

Given the tool's complexity (10 parameters, multiple actions including potentially destructive operations), the absence of annotations, and no output schema, the description is completely inadequate. It doesn't explain what the tool returns, what 'managing' CloudWAF instances entails, or how different actions affect the system. For a multi-action tool that could create, update, or delete resources, this minimal description leaves the agent with insufficient context to use the tool effectively.

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?

The schema description coverage is 100%, so all parameters are documented in the input schema itself. The description adds no additional parameter information beyond what's already in the structured schema. According to the scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no parameter information in the description, which applies here.

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

Purpose2/5

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

The description 'Manage CloudWAF instances' is essentially a tautology that restates the tool name 'manage_cloudwaf' without adding meaningful specificity. It doesn't clarify what 'manage' entails or what 'CloudWAF instances' are, nor does it distinguish this tool from its many siblings like 'manage_alerts', 'manage_blacklist', etc. The description lacks a clear verb+resource combination that would help an agent understand the tool's function.

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

Usage Guidelines1/5

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

The description provides absolutely no guidance on when to use this tool versus alternatives. With 27 sibling tools including many that manage related resources (sites, rules, alerts, etc.), the agent receives no help in selecting this specific tool for CloudWAF instance management. There's no mention of prerequisites, appropriate contexts, or comparison to other tools.

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/purpleax/FastlyMCP'

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