Skip to main content
Glama
purpleax

Fastly NGWAF MCP Server

by purpleax

delete_site_rule

Remove a specific security rule from a Fastly NGWAF site to manage web application firewall configurations.

Instructions

Delete a site-level rule

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
corpNameNoCorporation name (uses context default if not provided)
siteNameNoSite name (uses context default if not provided)
ruleIdYesRule ID to delete

Implementation Reference

  • Handler logic in the CallToolRequestSchema that resolves context, validates siteName, and calls the client deleteSiteRule method.
    case 'delete_site_rule':
        const { corpName: corpForDeleteSiteRule, siteName: siteForDeleteRule } = resolveContext(typedArgs);
        if (!siteForDeleteRule) {
            throw new Error('Site name is required. Please set context or provide siteName parameter.');
        }
        result = await client.deleteSiteRule(corpForDeleteSiteRule, siteForDeleteRule, typedArgs.ruleId);
        break;
  • Input schema defining parameters for the delete_site_rule tool: corpName, siteName (optional, uses context), required ruleId.
    inputSchema: {
        type: 'object',
        properties: {
            corpName: { type: 'string', description: 'Corporation name (uses context default if not provided)' },
            siteName: { type: 'string', description: 'Site name (uses context default if not provided)' },
            ruleId: { type: 'string', description: 'Rule ID to delete' },
        },
        required: ['ruleId'],
    },
  • server.js:616-628 (registration)
    Registration of the delete_site_rule tool in the tools list provided to the MCP server.
    {
        name: 'delete_site_rule',
        description: 'Delete a site-level rule',
        inputSchema: {
            type: 'object',
            properties: {
                corpName: { type: 'string', description: 'Corporation name (uses context default if not provided)' },
                siteName: { type: 'string', description: 'Site name (uses context default if not provided)' },
                ruleId: { type: 'string', description: 'Rule ID to delete' },
            },
            required: ['ruleId'],
        },
    },
  • Underlying API client method in FastlyNGWAFClient that performs the DELETE request to remove a site rule.
    async deleteSiteRule(corpName, siteName, ruleId) {
        await this.api.delete(`/corps/${corpName}/sites/${siteName}/rules/${ruleId}`);
        return { success: true };
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Delete' implies a destructive mutation, but the description doesn't state whether this action is reversible, what permissions are required, or what happens upon deletion (e.g., if related data is affected). For a destructive tool with zero annotation coverage, this is a significant gap in safety and operational context.

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 directly states the action and target. It's appropriately sized and front-loaded, making it easy to parse quickly 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 this is a destructive mutation tool with no annotations and no output schema, the description is incomplete. It lacks critical context such as confirmation of deletion, error handling, return values, or impact on related resources. The schema covers parameters well, but behavioral and output details are missing, making it inadequate for safe and informed use.

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%, so the schema fully documents all three parameters (corpName, siteName, ruleId) with their types and descriptions. The description adds no additional parameter semantics beyond implying 'site-level' relates to siteName. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Delete') and resource ('a site-level rule'), making the purpose immediately understandable. It distinguishes from sibling tools like 'delete_corp_rule' by specifying 'site-level' rather than corporate-level. However, it doesn't explicitly contrast with other deletion tools like 'delete_site' or 'delete_corp_rule' in the description itself.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing ruleId), when not to use it, or refer to sibling tools like 'delete_corp_rule' for corporate-level deletions. The agent must infer usage from the tool name and schema alone.

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