manage_persistence
Persistence data operations. action: services (list), get_data, store_data, statistics, summarize.
This record as markdown: /tools/deswong-openhab-mcp/manage-persistence.md
What manage_persistence does on Openhab
AI agents use manage_persistence to create or update resources in Openhab, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Openhab environment.
Why manage_persistence is rated Medium
The tool's primary write capability is 'store_data', allowing creation and modification of persistence records. This is reversible (data can be overwritten or cleared), so it does not qualify as Destructive.
From the tool's definition Tool description states 'store_data' as an action, which creates or modifies persistence data. While it also includes read-only actions (services, get_data, statistics, summarize), the presence of 'store_data' makes this a Write operation.
Attacks that exploit this kind of access
The rule that runs manage_persistence safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Openhab, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For manage_persistence, this is the rule to start with:
manage_persistence stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Openhab, apply this rule, and every manage_persistence call is checked against it from then on.
Questions about manage_persistence
Persistence data operations. action: services (list), get_data, store_data, statistics, summarize. It is categorised as a Write tool in the Openhab MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Openhab MCP server in PolicyLayer and add a rule for manage_persistence: 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 Openhab. Nothing to install.
manage_persistence 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 manage_persistence 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 manage_persistence. 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.
manage_persistence is provided by the Openhab MCP server (deswong/openhab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Openhab, and thousands of servers like it.
This server
Across the catalogue