Skip to main content
Glama
purpleax

Fastly NGWAF MCP Server

by purpleax

get_suspicious_ips

Retrieve suspicious IP addresses from Fastly's Next-Gen WAF to identify potential security threats and enhance web application protection.

Instructions

Get list of suspicious IP addresses

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
corpNameNoCorporation name (uses context default if not provided)
siteNameNoSite name (uses context default if not provided)
limitNoMaximum number of IPs to return

Implementation Reference

  • MCP tool handler in the CallToolRequestSchema switch statement that resolves the corporation and site context, validates siteName, and calls the underlying client.getSuspiciousIPs method.
    case 'get_suspicious_ips':
        const { corpName: corpForSuspicious, siteName: siteForSuspicious } = resolveContext(typedArgs);
        if (!siteForSuspicious) {
            throw new Error('Site name is required. Please set context or provide siteName parameter.');
        }
        result = await client.getSuspiciousIPs(corpForSuspicious, siteForSuspicious, typedArgs.limit);
        break;
  • Input schema definition for the get_suspicious_ips tool, specifying parameters for corpName, siteName, and optional limit.
    {
        name: 'get_suspicious_ips',
        description: 'Get list of suspicious IP addresses',
        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)' },
                limit: { type: 'number', description: 'Maximum number of IPs to return' },
            },
        },
    },
  • FastlyNGWAFClient helper method that makes an API GET request to retrieve suspicious IP addresses from the /suspiciousIPs endpoint.
    async getSuspiciousIPs(corpName, siteName, limit) {
        const params = new URLSearchParams();
        if (limit)
            params.append('limit', limit.toString());
        const response = await this.api.get(`/corps/${corpName}/sites/${siteName}/suspiciousIPs?${params.toString()}`);
        return response.data;
    }
  • server.js:814-816 (registration)
    Registration of the tools list handler, which includes get_suspicious_ips in the static tools array returned for ListToolsRequestSchema.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
        return { tools };
    });
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. It states this is a read operation ('Get'), but doesn't mention permissions, rate limits, data freshness, or what the output looks like (e.g., format, pagination). For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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 no wasted words. It's front-loaded with the core purpose, making it easy to parse quickly. Every word earns its place by conveying essential information without redundancy.

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 the tool's complexity (3 parameters, no output schema, no annotations), the description is incomplete. It doesn't explain the return values, how 'suspicious' is defined, or behavioral aspects like error handling. For a tool that likely involves security data, more context is needed to use it 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?

Schema description coverage is 100%, so the schema fully documents the three parameters (corpName, siteName, limit) with descriptions. The description adds no additional parameter information beyond what's in the schema, but since the schema is comprehensive, a baseline score of 3 is appropriate as the description doesn't need to compensate.

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

Purpose3/5

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

The description 'Get list of suspicious IP addresses' clearly states the action (get) and resource (suspicious IP addresses), but it's somewhat vague about scope and criteria. It doesn't specify what makes an IP 'suspicious' or how the list is generated, and it doesn't differentiate from sibling tools like 'manage_blacklist' or 'search_requests' which might also involve IP addresses.

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. With siblings like 'manage_blacklist' (which might handle IP blocking) and 'search_requests' (which could filter by IP), there's no indication of this tool's specific context or prerequisites, leaving the agent to guess based on the name 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