read_multiple_holding_registers
AI agents call read_multiple_holding_registers to retrieve information from Modbus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves data from Modbus holding registers. Reading holding registers is a non-destructive, query-like operation with no side effects. While Modbus systems control industrial/operational technology, a read-only operation on registers poses minimal risk compared to write or execute operations. The lack of description slightly reduces confidence, but the function name is unambiguous.
From the tool's definition Tool name 'read_multiple_holding_registers' clearly indicates a read operation on Modbus holding registers. Modbus read operations retrieve data without side effects.
Documented attack patterns abuse exactly the kind of access read_multiple_holding_registers gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Modbus, and nothing reaches the server without passing your rules. This is the rule we recommend for read_multiple_holding_registers:
{
"version": "1",
"default": "deny",
"tools": {
"read_multiple_holding_registers": {}
}
}read_multiple_holding_registers is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
read_multiple_holding_registers. It is categorised as a Read tool in the Modbus MCP Server, which means it retrieves data without modifying state.
Register the Modbus MCP server in PolicyLayer and add a rule for read_multiple_holding_registers: 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 Modbus. Nothing to install.
read_multiple_holding_registers 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 read_multiple_holding_registers 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 read_multiple_holding_registers. 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.
read_multiple_holding_registers is provided by the Modbus MCP server (kukapay/modbus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Modbus, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 Modbus tools catalogued and risk-classified — across an index of 43,000+ MCP servers.