get_api_endpoints

List available API endpoints from OPNsense

SERVEROPNsense MCP Server SOURCEfakebizprez/opnsense-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/fakebizprez-opnsense-mcp-server/get-api-endpoints.md

WHAT IT DOES

What get_api_endpoints does on OPNsense MCP Server

AI agents call get_api_endpoints to retrieve information from OPNsense MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_api_endpoints is rated Low

This tool performs a read-only retrieval of API endpoint information. It queries available endpoints but does not modify system state, execute commands, delete data, or commit financial transactions.

From the tool's definition Tool name 'get_api_endpoints' and description 'List available API endpoints from OPNsense' indicate a query/list operation that retrieves metadata about available API endpoints without modifying or executing actions.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_api_endpoints safely

PolicyLayer is an MCP gateway: it sits between your AI agents and OPNsense MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_api_endpoints, this is the rule to start with:

get_api_endpoints Allowed

get_api_endpoints is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_api_endpoints": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect OPNsense MCP Server, apply this rule, and every get_api_endpoints call is checked against it from then on.

FAQ

Questions about get_api_endpoints

What does the get_api_endpoints tool do? +

List available API endpoints from OPNsense. It is categorised as a Read tool in the OPNsense MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_api_endpoints? +

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

What risk level is get_api_endpoints? +

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

Can I rate-limit get_api_endpoints? +

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

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

get_api_endpoints is provided by the OPNsense MCP Server MCP server (fakebizprez/opnsense-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on OPNsense MCP Server, and thousands of servers like it.

This server

All 22 OPNsense MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →