Skip to main content
Glama
Sign In
cPanel MCP Server

cPanel MCP Server

by 0xHayd3n
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

block_ip

Prevent malicious traffic by blocking an IP address, range, or CIDR notation. Restrict unwanted connections to secure your server.

Instructions

Block an IP address or range

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ip": "<ip>"
    },
    "name": "block_ip"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipYesIP address, range (e.g., 10.0.0.0/24), or CIDR notation

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/5.0
Behavior2/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. It states the action but does not explain side effects (e.g., immediate effect, irreversibility, permissions needed, or impact on existing connections). The description is too terse for a security-relevant mutation.

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 one concise sentence, front-loaded with the action and target. No unnecessary words. It earns its place perfectly.

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

Completeness3/5

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

For a tool with a single parameter and a clear name, the description is minimally adequate. However, the lack of operational context (e.g., what 'block' means in terms of connectivity, persistence, or logging) is a gap. It is not as incomplete as more complex update tools but could benefit from one or two clarifiers.

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 already thoroughly documents the 'ip' parameter with format examples, and the description adds little beyond restating 'IP address or range'. Schema coverage is 100%, so baseline is 3. No extra semantic value is provided.

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

Purpose5/5

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

The description uses a specific verb ('block') and clearly names the resource ('IP address or range'). It naturally distinguishes from sibling tools like 'unblock_ip' and 'list_blocked_ips'.

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

Usage Guidelines3/5

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

Usage is implied but not explicitly stated. The description gives no direct guidance on when to use this tool versus alternatives, though the presence of sibling tools like 'unblock_ip' provides context. It doesn't offer exclusions or explicit decision rules.

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

Deploy Server

Other Tools