Low Risk

fleet_nginx_list

List all nginx site configs

How to control fleet_nginx_list ↓

What fleet_nginx_list does on Fleet

AI agents call fleet_nginx_list to retrieve information from Fleet without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why fleet_nginx_list needs a policy

This tool retrieves existing Nginx site configurations for inspection. It has no side effects, creates no changes, executes no code, and poses minimal risk. The blast radius of misuse is limited to information disclosure of Nginx configuration details (which may reveal hostnames, ports, or upstream targets but not credentials given the server's age-encrypted secrets design). Categorized as Read with low severity.

From the tool's definition Tool name is 'fleet_nginx_list' and description states 'List all nginx site configs' — purely a read/query operation that retrieves configuration data without modification or execution.

Documented attack patterns abuse exactly the kind of access fleet_nginx_list gives an agent:

How to control fleet_nginx_list

PolicyLayer is an MCP gateway — it sits between your AI agents and Fleet, and nothing reaches the server without passing your rules. This is the rule we recommend for fleet_nginx_list:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "fleet_nginx_list": {}
  }
}

fleet_nginx_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Fleet — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about fleet_nginx_list

What does the fleet_nginx_list tool do? +

List all nginx site configs. It is categorised as a Read tool in the Fleet MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on fleet_nginx_list? +

Register the Fleet MCP server in PolicyLayer and add a rule for fleet_nginx_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 Fleet. Nothing to install.

What risk level is fleet_nginx_list? +

fleet_nginx_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit fleet_nginx_list? +

Yes. Add a rate_limit block to the fleet_nginx_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 fleet_nginx_list completely? +

Set action: deny in the PolicyLayer policy for fleet_nginx_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 fleet_nginx_list? +

fleet_nginx_list is provided by the Fleet MCP server (wrxck/fleet). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Fleet tool call.

Start from Fleet, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

39 Fleet tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.