disable_hateoas · pfSense Enhanced MCP Server MCP

WHAT IT DOES

What disable_hateoas does on pfSense Enhanced MCP Server

AI agents use disable_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 disable_hateoas needs a policy

This tool modifies session-level API response formatting by disabling HATEOAS (Hypermedia As The Engine Of Application State) links. While it changes state, it is reversible (can be re-enabled), affects only the current session, has no data deletion or financial impact, and does not execute arbitrary code or dangerous operations.

From the tool's definition Tool name 'disable_hateoas' and description 'Disable HATEOAS links in API responses for this session' indicates modification of API response behavior/configuration settings.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

disable_hateoas Rate-limited

disable_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": {
    "disable_hateoas": {
      "limits": [
        {
          "counter": "disable_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 disable_hateoas

What does the disable_hateoas tool do? +

Disable 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 disable_hateoas? +

Register the pfSense Enhanced MCP Server MCP server in PolicyLayer and add a rule for disable_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 disable_hateoas? +

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

Can I rate-limit disable_hateoas? +

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

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

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