enable_hateoas · pfSense Enhanced MCP Server MCP

WHAT IT DOES

What enable_hateoas does on pfSense Enhanced MCP Server

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

WHY IT NEEDS A POLICY

Why enable_hateoas needs a policy

This tool modifies session state by toggling HATEOAS hypermedia links on/off. While reversible (can be disabled again) and not destructive, it constitutes a configuration change to the API behavior. The impact is localized to the current session and only affects response format, making it low-severity.

From the tool's definition Tool description states 'Enable HATEOAS links in API responses for this session' — this modifies the configuration or state of the API session to include hypermedia links in subsequent responses.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

enable_hateoas Rate-limited

enable_hateoas 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": {
    "enable_hateoas": {
      "limits": [
        {
          "counter": "enable_hateoas_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 Enhanced MCP Server, so you can run agents against it safely.

FAQ

Questions about enable_hateoas

What does the enable_hateoas tool do? +

Enable HATEOAS links in API responses for this session. It is categorised as a Write tool in the pfSense Enhanced MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on enable_hateoas? +

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

What risk level is enable_hateoas? +

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

Can I rate-limit enable_hateoas? +

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

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

enable_hateoas is provided by the pfSense Enhanced MCP Server MCP server (mmaxwellcb/pfsesen_mcp_2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.