get_device_egress_fail_posture

SERVERBusymate DevTools SOURCEhttps://mcp.busymate.dev

Low RISK CLASS

Category Read

Parameters 20 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-busymate-busymate-devtools/get-device-egress-fail-posture.md

WHAT IT DOES

What get_device_egress_fail_posture does on Busymate DevTools

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

Parameter	Type	Required	Description
`deviceName`	string	—
`device_uuid`	string	—

Parameters from the server's own tool schema.

RISK

Why get_device_egress_fail_posture is rated Low

Even though get_device_egress_fail_posture only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_device_egress_fail_posture safely

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

get_device_egress_fail_posture Allowed

get_device_egress_fail_posture 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_device_egress_fail_posture": {}
  }
}

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

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

FAQ

Questions about get_device_egress_fail_posture

What does the get_device_egress_fail_posture tool do? +

Read a device's PAC egress FAIL POSTURE (#1657) — what the proxy does when the device is handed the #76 PAC DIRECT fallback (its PAC-fetch source IP is not yet in the CONNECT-source admission allowlist, routine on CGNAT). The setting egressFailPosture ∈ open | closed | auto rides settings_{global,device}.data and is resolved device→user→service→global by effective_settings_for_device (like the external proxy). Meanings: open → serve DIRECT (stay online, but the device egresses from its REAL IP — a leak for an external-proxy/country-pinned device); closed → serve a HOLD/no-egress PAC (proxy-only, NEVER DIRECT) so the real IP is never used; auto (the DARK-safe DEFAULT) → closed IFF an external proxy is enabled for the device, open otherwise — i.e. fail-CLOSED for country/IP-pinned devices, fail-OPEN for everyone else. Returns { device_uuid, effective, is_default, default, global, device } — effective is the merged value the proxy sees (the auto default made explicit), with the per-tier raw values (global/device, null when unset) for the breakdown. Owner-scoped: without devices:view you may still read YOUR OWN device by uuid/name. Read-only. It is categorised as a Read tool in the Busymate DevTools MCP Server, which means it retrieves data without modifying state.

What parameters does get_device_egress_fail_posture accept? +

get_device_egress_fail_posture accepts 2 parameters: deviceName, device_uuid. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_device_egress_fail_posture? +

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

What risk level is get_device_egress_fail_posture? +

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

Can I rate-limit get_device_egress_fail_posture? +

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

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

get_device_egress_fail_posture is provided by the Busymate DevTools MCP server (https://mcp.busymate.dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Busymate DevTools, and thousands of servers like it.

This server

All 44 Busymate DevTools 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 →