automation_insert · Vicarius vRx MCP Server MCP

WHAT IT DOES

What automation_insert does on Vicarius vRx MCP Server

AI agents use automation_insert 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_insert needs a policy

The tool creates or adds new automation instances via PUT request, which is a reversible write operation. The context of 'automation' objects in a vulnerability management system (Vicarius vRx) suggests this could create automation rules or tasks, but the operation is not destructive and can be reversed.

From the tool's definition Tool name contains 'insert' and HTTP method is PUT; description states 'insert instance of the object' with 'Requires a JSON request body.' This creates new automation records.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

automation_insert Rate-limited

automation_insert 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_insert": {
      "limits": [
        {
          "counter": "automation_insert_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_insert

What does the automation_insert tool do? +

automation \u00b7 PUT /automation/insert \u2014 insert 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_insert? +

Register the Vicarius vRx MCP Server MCP server in PolicyLayer and add a rule for automation_insert: 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_insert? +

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

Can I rate-limit automation_insert? +

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

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

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