device_status

Check if a device is online and reachable.

Server Kc Modbus kerberosclaw/kc_modbus_mcp
Category Read
Risk class Low
Parameters 00 required

What device_status does on Kc Modbus

AI agents call device_status to retrieve information from Kc Modbus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why device_status needs a policy

This tool performs a simple health check query of a Modbus device's connectivity status. It has no side effects, does not modify device state, and does not execute commands. It is purely informational, retrieving current state data. The low severity reflects minimal risk—a misused status check cannot damage systems or data.

From the tool's definition Tool name 'device_status' and description 'Check if a device is online and reachable' indicate a diagnostic query operation that retrieves status information without modifying or executing external operations.

Questions about device_status

What does the device_status tool do? +

Check if a device is online and reachable. It is categorised as a Read tool in the Kc Modbus MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on device_status? +

Register the Kc Modbus MCP server in PolicyLayer and add a rule for 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 Kc Modbus. Nothing to install.

What risk level is device_status? +

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

Can I rate-limit device_status? +

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

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

device_status is provided by the Kc Modbus MCP server (kerberosclaw/kc_modbus_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.