List all Things registered in the ThingWorx model. Returns Thing names, descriptions, and parent ThingTemplate. The standard read path for an agent that needs to discover the industrial asset inventory.
AI agents call list_things 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.
list_things retrieves and enumerates existing Things without side effects. This is a pure discovery/query operation over read-only asset metadata. The moderate information disclosure risk (industrial asset names and structure) is typical of Read-category tools and warrants only low severity in an IIoT context where the server already employs env-gated safety controls for writes and invocations.
From the tool's definition Tool is described as 'The standard read path for an agent that needs to discover the industrial asset inventory' and 'Returns Thing names, descriptions, and parent ThingTemplate.' No modification, deletion, or action invocation occurs.
Attacks that exploit this kind of access
List all Things registered in the ThingWorx model. Returns Thing names, descriptions, and parent ThingTemplate. The standard read path for an agent that needs to discover the industrial asset inventory. 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 list_things: 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.
list_things 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 list_things 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 list_things. 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.
list_things 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 →