update_global_ruleset · OpenRemote MCP Server MCP

WHAT IT DOES

What update_global_ruleset does on OpenRemote MCP Server

AI agents use update_global_ruleset to create or update resources in OpenRemote MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OpenRemote MCP Server environment.

WHY IT NEEDS A POLICY

Why update_global_ruleset needs a policy

The tool modifies existing configuration data (a ruleset) that affects operational behavior at a global level. This is a Write operation (reversible modification) rather than Destructive (no deletion). However, the 'global' scope and the fact that rulesets control automation/business logic in OpenRemote systems means misuse could have high blast radius—affecting many assets, users, or system behaviors.

From the tool's definition Tool description explicitly states 'Update an existing global ruleset', indicating modification of data. 'Global' scope suggests system-wide impact affecting multiple resources or tenants.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_global_ruleset Rate-limited

update_global_ruleset 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_global_ruleset": {
      "limits": [
        {
          "counter": "update_global_ruleset_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches OpenRemote MCP Server, so you can run agents against it safely.

FAQ

Questions about update_global_ruleset

What does the update_global_ruleset tool do? +

Update an existing global ruleset. First retrieve it with 'get_global_ruleset', modify, then call this. It is categorised as a Write tool in the OpenRemote MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_global_ruleset? +

Register the OpenRemote MCP Server MCP server in PolicyLayer and add a rule for update_global_ruleset: 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 OpenRemote MCP Server. Nothing to install.

What risk level is update_global_ruleset? +

update_global_ruleset is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_global_ruleset? +

Yes. Add a rate_limit block to the update_global_ruleset 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.

How do I block update_global_ruleset completely? +

Set action: deny in the PolicyLayer policy for update_global_ruleset. 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.

What MCP server provides update_global_ruleset? +

update_global_ruleset is provided by the OpenRemote MCP Server MCP server (openremote/service-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.