renew_certificate · Nginx Proxy Manager MCP: Risk & Policy

WHAT IT DOES

What renew_certificate does on Nginx Proxy Manager MCP

AI agents use renew_certificate 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 IT NEEDS A POLICY

Why renew_certificate needs a policy

Renewing a certificate is a reversible modification operation that updates certificate data rather than destroying it. It does not execute arbitrary code, move financial resources, or delete data irreversibly. The blast radius is medium because certificate renewal affects TLS/SSL infrastructure and could impact service availability if misconfigured, but the operation itself is a standard, recoverable state change.

From the tool's definition Tool name 'renew_certificate' and context indicate it modifies certificate state by renewing an existing Let's Encrypt SSL certificate. The description is incomplete but the action is clearly a modification operation, not data deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

renew_certificate Rate-limited

renew_certificate stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "renew_certificate": {
      "limits": [
        {
          "counter": "renew_certificate_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Nginx Proxy Manager MCP, so you can run agents against it safely.

FAQ

Questions about renew_certificate

What does the renew_certificate tool do? +

Renew a Let. 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 renew_certificate? +

Register the Nginx Proxy Manager MCP server in PolicyLayer and add a rule for renew_certificate: 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 renew_certificate? +

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

Can I rate-limit renew_certificate? +

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

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

renew_certificate 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.