Use the PlcProgram.Read method to read a single variable from a CPU. To call the PlcProgram.Read method, you need the
AI agents call PlcProgram-Read to retrieve information from ThinkPLC-MCP 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 a PLC controller without altering it, which fits the Read category. However, severity is elevated to medium rather than low because: (1) PLC systems control critical industrial/physical processes where unauthorized reads could enable reconnaissance for attacks; (2) the context involves SIEMENS S7-1500/1200 controllers which typically manage safety-critical operations; (3) reading…
From the tool's definition Tool name is 'PlcProgram-Read' and description states it 'read[s] a single variable from a CPU' with no modification or deletion of data.
Documented attack patterns abuse exactly the kind of access PlcProgram-Read gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ThinkPLC-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for PlcProgram-Read:
{
"version": "1",
"default": "deny",
"tools": {
"PlcProgram-Read": {}
}
}PlcProgram-Read 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.
Use the PlcProgram.Read method to read a single variable from a CPU. To call the PlcProgram.Read method, you need the. It is categorised as a Read tool in the ThinkPLC-MCP MCP Server, which means it retrieves data without modifying state.
Register the ThinkPLC- MCP server in PolicyLayer and add a rule for PlcProgram-Read: 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 ThinkPLC-MCP. Nothing to install.
PlcProgram-Read 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 PlcProgram-Read 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 PlcProgram-Read. 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.
PlcProgram-Read is provided by the ThinkPLC- MCP server (mrwan84/thinkplc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ThinkPLC-MCP, 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.
23 ThinkPLC-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.