Write a new value to a Property on a Thing. Gated by THINGWORX_ALLOW_WRITE=true because property writes can change the state of real industrial equipment (setpoints, modes, configuration). The MCP refuses to write unless the operator has explicitly authorized it.
AI agents use write_property to create or update resources in Thingworx — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Thingworx environment.
This tool creates or modifies data on ThingWorx Things (industrial assets). While the modifications could have significant real-world impact on industrial equipment, they are technically reversible—a property can be written again to a different value. This distinguishes it from Destructive (which is irreversible).
From the tool's definition Tool description states: 'Write a new value to a Property on a Thing' and 'property writes can change the state of real industrial equipment (setpoints, modes, configuration)'.
Attacks that exploit this kind of access
Write a new value to a Property on a Thing. Gated by THINGWORX_ALLOW_WRITE=true because property writes can change the state of real industrial equipment (setpoints, modes, configuration). The MCP refuses to write unless the operator has explicitly authorized it. It is categorised as a Write tool in the Thingworx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Thingworx MCP server in PolicyLayer and add a rule for write_property: 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.
write_property is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the write_property 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 write_property. 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.
write_property 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 →