pfsense_create_services_haproxy_settings_email_mailer

WHAT IT DOES

What pfsense_create_services_haproxy_settings_email_mailer does on Pfsense

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

WHY IT NEEDS A POLICY

Why pfsense_create_services_haproxy_settings_email_mailer needs a policy

The tool appears to create or modify HAProxy email mailer settings based on its name structure. This is a Write operation (creates/modifies configuration reversibly) rather than Read, Execute, or Destructive. Severity is medium because misconfigured email settings could disrupt critical alert notifications from the firewall, but does not directly compromise network security or permit code execution.

From the tool's definition Tool name contains 'create' and 'settings' indicating modification of HAProxy email mailer configuration in pfSense. Description is empty, limiting precision.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pfsense_create_services_haproxy_settings_email_mailer Rate-limited

pfsense_create_services_haproxy_settings_email_mailer 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": {
    "pfsense_create_services_haproxy_settings_email_mailer": {
      "limits": [
        {
          "counter": "pfsense_create_services_haproxy_settings_email_mailer_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 Pfsense, so you can run agents against it safely.

FAQ

Questions about pfsense_create_services_haproxy_settings_email_mailer

What does the pfsense_create_services_haproxy_settings_email_mailer tool do? +

pfsense_create_services_haproxy_settings_email_mailer. It is categorised as a Write tool in the Pfsense MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on pfsense_create_services_haproxy_settings_email_mailer? +

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

What risk level is pfsense_create_services_haproxy_settings_email_mailer? +

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

Can I rate-limit pfsense_create_services_haproxy_settings_email_mailer? +

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

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

pfsense_create_services_haproxy_settings_email_mailer is provided by the Pfsense MCP server (abl030/pfsense-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.