get_device_status

Get the latest device_status row (online flag, last_heartbeat_at, ip, vpn_state, source).

SERVERBusymate DevTools SOURCEhttps://mcp.busymate.dev

Low RISK CLASS

Category Read

Parameters 20 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/dev-busymate-busymate-devtools/get-device-status.md

WHAT IT DOES

What get_device_status does on Busymate DevTools

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

This is a simple query/fetch operation that retrieves device status metadata. It has no side effects, does not execute code, does not modify data, and does not move money. The information returned (online status, last heartbeat timestamp, IP address, VPN state, source) is operational telemetry with no destructive capability.

From the tool's definition Tool name 'get_device_status' and description 'Get the latest device_status row' indicate a retrieval operation with no modification or execution. Returns status fields: online flag, last_heartbeat_at, ip, vpn_state, source.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_device_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_status, this is the rule to start with:

get_device_status Allowed

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

FAQ

Questions about get_device_status

What does the get_device_status tool do? +

Get the latest device_status row (online flag, last_heartbeat_at, ip, vpn_state, source). 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_status accept? +

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

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

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

Can I rate-limit get_device_status? +

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

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

get_device_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 32 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 →