AI agents call get_thing_template to retrieve information from Thingworx without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only query operation that fetches metadata about a ThingTemplate definition. It has no side effects on the industrial asset graph or its state. The tool returns structural information useful for understanding template composition but does not alter, execute, or destroy any data.
From the tool's definition Tool retrieves and returns the full definition of a ThingTemplate by name, including property, service, event signatures, parent template, and implemented ThingShapes. No modification, invocation, or deletion occurs.
Attacks that exploit this kind of access
Get the full definition of a ThingTemplate by name, including property + service + event signatures, parent template, and implemented ThingShapes. It is categorised as a Read tool in the Thingworx MCP Server, which means it retrieves data without modifying state.
Register the Thingworx MCP server in PolicyLayer and add a rule for get_thing_template: 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 Thingworx. Nothing to install.
get_thing_template 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 get_thing_template 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 get_thing_template. 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.
get_thing_template is provided by the Thingworx MCP server (nobanks/thingworx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →