automations \u00b7 GET /v1/automations/{id} \u2014 Returns automation by id Required: id.
AI agents call automations_automations_2 to retrieve information from Vicarius vRx MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves automation data by ID without modifying, executing, deleting, or moving any data. It falls squarely into the Read category. The severity is low because retrieving automation configuration data poses minimal risk—it does not execute any actions, delete resources, or trigger financial transactions.
From the tool's definition Tool is described as a GET endpoint that 'Returns automation by id', which is a retrieval operation with no side effects. The HTTP method GET and the verb 'Returns' indicate this is a read-only query operation.
Attacks that exploit this kind of access
automations \u00b7 GET /v1/automations/{id} \u2014 Returns automation by id Required: id. It is categorised as a Read tool in the Vicarius vRx MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Vicarius vRx MCP Server MCP server in PolicyLayer and add a rule for automations_automations_2: 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.
automations_automations_2 is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the automations_automations_2 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 automations_automations_2. 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.
automations_automations_2 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →