ap_https

Test an HTTPS GET from an AP's perspective (async, polls ~60s). timeout: 1-10s.

SERVERHpe Networking SOURCEsecure-ssid/hpe-networking-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hpe-networking-mcp/ap-https.md

WHAT IT DOES

What ap_https does on Hpe Networking

AI agents invoke ap_https to trigger actions in Hpe Networking. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why ap_https is rated High

This tool causes an AP (Access Point) to perform an outbound HTTPS GET request, which is an active network operation with external side effects. It is not merely reading local data — it initiates a real network action from a device. This fits the Execute category.

From the tool's definition 'Test an HTTPS GET from an AP's perspective (async, polls ~60s)' — triggers an external network operation (HTTPS GET request) executed from a device

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ap_https safely

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

ap_https Rate-limited

ap_https stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ap_https": {
      "limits": [
        {
          "counter": "ap_https_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Hpe Networking, apply this rule, and every ap_https call is checked against it from then on.

FAQ

Questions about ap_https

What does the ap_https tool do? +

Test an HTTPS GET from an AP's perspective (async, polls ~60s). timeout: 1-10s. It is categorised as a Execute tool in the Hpe Networking MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on ap_https? +

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

What risk level is ap_https? +

ap_https is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit ap_https? +

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

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

ap_https is provided by the Hpe Networking MCP server (secure-ssid/hpe-networking-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Hpe Networking, and thousands of servers like it.

This server

All 595 Hpe Networking tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →