automation_update · Vicarius vRx MCP Server MCP

WHAT IT DOES

What automation_update does on Vicarius vRx MCP Server

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

WHY IT NEEDS A POLICY

Why automation_update needs a policy

This tool creates or modifies data reversibly through an update operation (POST to update endpoint). It changes automation settings but does not delete, destroy, or execute arbitrary operations. The sibling tools include destructive operations (automation_delete) and execute operations (automation_insert creates new records), but this specific tool is limited to updates.

From the tool's definition Tool performs POST /automation/update to 'Update instance of the object', modifying automation configuration data

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

automation_update Rate-limited

automation_update 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": {
    "automation_update": {
      "limits": [
        {
          "counter": "automation_update_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 Vicarius vRx MCP Server, so you can run agents against it safely.

FAQ

Questions about automation_update

What does the automation_update tool do? +

automation \u00b7 POST /automation/update \u2014 Update instance of the object Requires a JSON request body. It is categorised as a Write tool in the Vicarius vRx 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 automation_update? +

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

What risk level is automation_update? +

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

Can I rate-limit automation_update? +

Yes. Add a rate_limit block to the automation_update 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 automation_update completely? +

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

automation_update is provided by the Vicarius vRx MCP Server MCP server (space-c0wboy/vicarius-vrx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.