get_device_egress_status

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-status.md

WHAT IT DOES

What get_device_egress_status does on Busymate DevTools

AI agents call get_device_egress_status 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_status is rated Low

Even though get_device_egress_status 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_status 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_status, this is the rule to start with:

get_device_egress_status Allowed

get_device_egress_status 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_status": {}
  }
}

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_status call is checked against it from then on.

FAQ

Questions about get_device_egress_status

What does the get_device_egress_status tool do? +

Read a device's egress-IP set (#1432) — the device→proxy INGRESS / CONNECT-source ADMISSION IPs the proxy allowlists for it (the addresses it will ACCEPT this device's CONNECTs FROM), PLUS any manual dev overrides. These are the CONNECT-source ADMISSION IPs, NOT the target-visible egress ORIGIN the destination server sees (that origin is governed by the device's external (upstream) proxy — see set_device_external_proxy). Each row carries ip, source ('proxy' = an automatic /allocate row, rolling 48h window + 10-most-recent-per-device cap; 'manual' = a TTL'd dev override, EXEMPT from the cap), first_seen_at/last_seen_at, expires_at (manual only), set_by (who set a manual override), hit_count, and a derived active flag using the SAME window the kernel ipset feed (active_egress_ips) uses — proxy: last_seen within 48h; manual: not yet expired — so active_count is the set currently allowlisted for the device. 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_status accept? +

get_device_egress_status 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_status? +

Register the Busymate DevTools MCP server in PolicyLayer and add a rule for get_device_egress_status: 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_status? +

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

Can I rate-limit get_device_egress_status? +

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

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

get_device_egress_status 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_task_status on 0rca Dojo MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

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