Skip to main content
Glama
Sign In
cPanel MCP Server

cPanel MCP Server

by 0xHayd3n
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

enable_modsecurity_domain

Protect your websites by enabling ModSecurity on selected domains. Pass a comma-separated domain list to activate the web application firewall.

Instructions

Enable ModSecurity for specific domains

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": {
      "domains": "<domains>"
    },
    "name": "enable_modsecurity_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsYesComma-separated list of domains to enable ModSecurity on

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.3/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 merely restates the action without explaining side effects, reversibility, required permissions, or the outcome of the operation. For a mutation tool, this is a minimal disclosure.

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 concise sentence with no redundant words. It is appropriately sized for the tool's simplicity, earning top marks for efficiency.

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?

Given the tool's simplicity (1 parameter, no annotations, no output schema), the description is adequate but leaves gaps. It doesn't mention whether the operation is idempotent, what errors might occur, or what the return value indicates. Still, it covers the core purpose sufficiently for a simple mutation.

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% — the 'domains' parameter is described as 'Comma-separated list of domains to enable ModSecurity on'. The description adds no extra meaning beyond this, matching the baseline score of 3.

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 'Enable ModSecurity for specific domains' uses a specific verb and resource, clearly distinguishing from sibling tools like enable_modsecurity (likely global) and disable_modsecurity_domain (opposite action). The scope is explicitly 'specific domains', making the purpose unambiguous.

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 such as enable_modsecurity or disable_modsecurity_domain. There is no mention of exclusions, prerequisites, or context that would help an agent choose this tool over others.

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