get_device_settings
Read settings_device for one device (device_uuid or deviceName).
This record as markdown: /tools/dev-busymate-busymate-devtools/get-device-settings.md
What get_device_settings does on Busymate DevTools
AI agents call get_device_settings 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.
Why get_device_settings is rated Low
This tool retrieves device settings configuration without modifying, executing code, or deleting data. It is a straightforward read operation with minimal security risk unless sensitive settings are exposed, but the tool itself performs no side effects or destructive actions.
From the tool's definition Tool name contains 'get_' and description explicitly states 'Read settings_device' with parameters (device_uuid or deviceName) for retrieval only.
Attacks that exploit this kind of access
The rule that runs get_device_settings 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_settings, this is the rule to start with:
get_device_settings is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Busymate DevTools, apply this rule, and every get_device_settings call is checked against it from then on.
Questions about get_device_settings
Read settings_device for one device (device_uuid or deviceName). It is categorised as a Read tool in the Busymate DevTools MCP Server, which means it retrieves data without modifying state.
get_device_settings accepts 2 parameters: deviceName, device_uuid. The full parameter table on this page comes from the server's own tool schema.
Register the Busymate DevTools MCP server in PolicyLayer and add a rule for get_device_settings: 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.
get_device_settings 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 get_device_settings 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 get_device_settings. 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.
get_device_settings 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.
More on Busymate DevTools, and thousands of servers like it.
This server
Across the catalogue