update_rule
AI agents use update_rule to create or update resources in SmartThingsMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SmartThingsMCP environment.
The 'update_rule' tool modifies existing automation rules reversibly. While the description is empty (lowering confidence slightly), the name and context indicate this creates or modifies data without permanent deletion. It could have high severity due to the potential for an AI agent to misconfigure critical home automation rules, affecting security, safety, or comfort.
From the tool's definition Tool name is 'update_rule' indicating modification of automation rules within the SmartThings ecosystem. Sibling tools show this server manages critical smart home infrastructure including scenes, locations, and automation rules.
Attacks that exploit this kind of access
update_rule. It is categorised as a Write tool in the SmartThingsMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SmartThings MCP server in PolicyLayer and add a rule for update_rule: 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 SmartThingsMCP. Nothing to install.
update_rule 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 update_rule 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 update_rule. 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.
update_rule is provided by the SmartThings MCP server (technohead/smartthings-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 →