This API method provides the system time of the CPU. If you have synchronized the system time of the CPU, for example via the TIA Portal function
AI agents call Plc-ReadSystemTime 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 queries and returns the current system time from a PLC controller. It is a read-only operation that retrieves data without altering state, executing commands, or causing destructive effects. The low severity reflects minimal blast radius—an AI agent misusing this tool could only obtain time information, which poses no operational, data integrity, or safety risk.
From the tool's definition Tool name 'Plc-ReadSystemTime' and description explicitly state it 'provides the system time of the CPU' — a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access Plc-ReadSystemTime 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 Plc-ReadSystemTime:
{
"version": "1",
"default": "deny",
"tools": {
"Plc-ReadSystemTime": {}
}
} Plc-ReadSystemTime 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.
This API method provides the system time of the CPU. If you have synchronized the system time of the CPU, for example via the TIA Portal function. 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 Plc-ReadSystemTime: 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.
Plc-ReadSystemTime 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 Plc-ReadSystemTime 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 Plc-ReadSystemTime. 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.
Plc-ReadSystemTime 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.