update_access_list

Update an existing access list

Server Nginx Proxy Manager MCP verybigsad/nginx-proxy-manager-mcp
Category Write
Risk class Medium
Parameters 00 required

What update_access_list does on Nginx Proxy Manager MCP

AI agents use update_access_list to create or update resources in Nginx Proxy Manager MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nginx Proxy Manager MCP environment.

Why update_access_list needs a policy

The tool modifies (but does not delete) access list configurations, which are security-sensitive resources that control which clients can access proxy hosts. Misuse could alter access permissions to web services, allowing or denying legitimate traffic. This is categorized as Write rather than Execute because it modifies configuration state rather than triggering external operations.

From the tool's definition Tool name 'update_access_list' and description 'Update an existing access list' indicate modification of existing access control configuration data. This is a reversible write operation on a critical security control mechanism.

Questions about update_access_list

What does the update_access_list tool do? +

Update an existing access list. It is categorised as a Write tool in the Nginx Proxy Manager MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_access_list? +

Register the Nginx Proxy Manager MCP server in PolicyLayer and add a rule for update_access_list: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Nginx Proxy Manager MCP. Nothing to install.

What risk level is update_access_list? +

update_access_list is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_access_list? +

Yes. Add a rate_limit block to the update_access_list rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block update_access_list completely? +

Set action: deny in the PolicyLayer policy for update_access_list. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides update_access_list? +

update_access_list is provided by the Nginx Proxy Manager MCP server (verybigsad/nginx-proxy-manager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.