Use the Api.Version method to request the current version number of the Web API. You can draw conclusions from the version number: • The functions supported by the CPU version • The hardware functional status of the CPU This information lets you implement applications that dynamically adapt to th...
AI agents call Api-Version 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.
Api-Version is a read-only operation that queries API metadata (version number) to enable version detection and feature adaptation. It performs no modifications, does not execute code or commands, does not delete data, and does not initiate financial transactions.
From the tool's definition Tool requests the current version number of the Web API; it retrieves information only and explicitly states 'No authorization is required for calling the Api.Version method', indicating a query operation with no side effects.
Documented attack patterns abuse exactly the kind of access Api-Version 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 Api-Version:
{
"version": "1",
"default": "deny",
"tools": {
"Api-Version": {}
}
}Api-Version 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 Api.Version method to request the current version number of the Web API. You can draw conclusions from the version number: • The functions supported by the CPU version • The hardware functional status of the CPU This information lets you implement applications that dynamically adapt to the scope of functions offered by the contacted CPU. An application can support multiple CPU versions. No authorization is required for calling the Api.Version method. 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 Api-Version: 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.
Api-Version 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 Api-Version 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 Api-Version. 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.
Api-Version 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.