Build a documentation-backed checklist and source pack for captive portal planning or troubleshooting.
AI agents call prepare_captive_portal_pack to retrieve information from UserGate MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool assembles documentation and checklists from a local corpus for planning/troubleshooting purposes. It retrieves and compiles information rather than modifying systems, executing commands, or affecting live infrastructure. No write, destructive, financial, or execution side effects are indicated.
From the tool's definition Build a documentation-backed checklist and source pack for captive portal planning or troubleshooting
Attacks that exploit this kind of access
Build a documentation-backed checklist and source pack for captive portal planning or troubleshooting. It is categorised as a Read tool in the UserGate MCP MCP Server, which means it retrieves data without modifying state.
Register the UserGate MCP server in PolicyLayer and add a rule for prepare_captive_portal_pack: 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 UserGate MCP. Nothing to install.
prepare_captive_portal_pack is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the prepare_captive_portal_pack 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.
Set action: deny in the PolicyLayer policy for prepare_captive_portal_pack. 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.
prepare_captive_portal_pack is provided by the UserGate MCP server (neonsummit/usergate-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →