ncloud-gov-mcp-server

ncloud_remove_acg_inbound_rule

DestructiveIdempotent

Remove an inbound rule from an Access Control Group to manage network permissions. Set confirm=true to execute the deletion.

Instructions

⚠️ Destructive: Remove an inbound rule from an Access Control Group. Set confirm=true to execute.

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": {
      "vpcNo": "<vpcNo>",
      "accessControlGroupNo": "<accessControlGroupNo>",
      "protocolTypeCode": "<protocolTypeCode>"
    },
    "name": "ncloud_remove_acg_inbound_rule"
  }
}

Input Schema

Name	Required	Description
`vpcNo`	Yes	VPC number (required)
`confirm`	No	Must be true to actually execute the destructive operation
`ipBlock`	No	IP block in CIDR format. Cannot be used with accessControlGroupSequence.
`portRange`	No	Port range (e.g., 80, 1-65535). Required if protocol is TCP or UDP.
`protocolTypeCode`	Yes	Protocol type code (TCP, UDP, ICMP, or protocol number)
`accessControlGroupNo`	Yes	ACG number to remove rule from (required)
`accessControlGroupSequence`	No	Source ACG number. Cannot be used with ipBlock.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Beyond the destructiveHint annotation, the description adds crucial behavioral context: 'Set confirm=true to execute.' This explains the safety confirmation mechanism not visible in annotations, though it does not elaborate on other behavioral aspects like idempotency.

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 the destructive warning front-loaded. Every word provides value, and there is no redundancy or fluff.

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?

While the schema and annotations cover parameters and safety, the description lacks context about prerequisites, mutual exclusions (e.g., ipBlock vs accessControlGroupSequence), and what happens after removal. It is minimally adequate but not rich.

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 parameter semantics are fully covered by the schema. The description's mention of confirm=true adds no new information beyond what the schema already states for that parameter.

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 explicitly states 'Remove an inbound rule from an Access Control Group' using a specific verb and resource. It clearly distinguishes from sibling tools like ncloud_add_acg_inbound_rule and ncloud_remove_acg_outbound_rule.

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?

The description does not provide explicit guidance on when to use this tool versus alternatives. The name and context imply usage for removing inbound ACG rules, but there is no mention of exclusions or references to sibling tools.

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

Deploy Server