Nginx Proxy Manager MCP

Overview Schema Source Related Servers Discussions Admin

Delete Access List

delete_access_list

Permanently remove an Nginx Proxy Manager access list by ID when it is no longer needed. Preview the request with dry_run=True before deleting, since deletion cannot be undone.

Instructions

Permanently delete an access list by ID from NPM. Use update_access_list to retain the list and change its rules; confirm the ID with list_access_lists first. Deletion cannot be undone and may affect hosts that reference the list. Returns True on success. Set dry_run=True to preview the exact request without changing NPM.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	ID of the access list, from the matching list tool.
`dry_run`	No	When True, return the exact request preview without changing NPM.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.5.2Oct 16, 2026

addedInput schema / properties / dry_run / description

Added value: +"When True, return the exact request preview without changing NPM."

addedInput schema / properties / id / description

Added value: +"ID of the access list, from the matching list tool."

First observedv0.5.1Oct 16, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does so: it declares the operation is permanent and irreversible, warns that referencing hosts may be affected, states the return value (True on success), and documents the dry_run preview behavior. This is exactly the destructive-operation context an agent needs.

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?

Four tight sentences, each earning its place: action, alternative, prerequisite, consequences, return value, and preview flag. The destructive action is front-loaded, followed by the safe alternative.

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

Completeness5/5

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

An output schema exists and the description still notes the True-on-success return, and all the operational risk of an irreversible delete is disclosed. Nothing needed to invoke this tool safely is missing.

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% and both parameters are already documented in the schema, including dry_run's preview semantics and the ID's origin. The description reinforces this but adds no syntax or format detail beyond what the schema provides, so baseline 3 applies.

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?

States a specific verb+resource combination ('Permanently delete an access list by ID from NPM') and explicitly distinguishes itself from update_access_list and list_access_lists. An agent can select this tool without opening any sibling schema.

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

Usage Guidelines5/5

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

Gives explicit routing: use update_access_list to keep the list and change rules, and confirm the ID with list_access_lists first. Both the 'when to use this' and the 'when to use something else' conditions are stated, plus a prerequisite step.

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