This record as markdown: /tools/deswong-openhab-mcp/remediate.md
What remediate does on Openhab
AI agents invoke remediate to trigger actions in Openhab. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why remediate is rated High
The term 'bulk remediation' implies executing corrective actions across multiple entities, which goes beyond simple writes and involves triggering external operations or system-level changes at scale. 'Generation' suggests creating new configurations. The bulk nature and remediation context (fixing/correcting issues) implies Execute-level impact. Confidence is moderate due to the vague description.
From the tool's definition 'Bulk remediation and generation' - performs bulk operations that likely modify or create multiple items/rules/configurations
Attacks that exploit this kind of access
The rule that runs remediate 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 remediate, this is the rule to start with:
remediate stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 remediate call is checked against it from then on.
Questions about remediate
Bulk remediation and generation. It is categorised as a Execute tool in the Openhab MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Openhab MCP server in PolicyLayer and add a rule for remediate: 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.
remediate is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the remediate 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 remediate. 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.
remediate 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.
Across the catalogue