automation_search_all

automation \u00b7 POST /automation/searchAll \u2014 Returns events Required: q, from, size.

Server Vicarius vRx MCP Server space-c0wboy/vicarius-vrx-mcp-server
Category Read
Risk class Low
Parameters 00 required

What automation_search_all does on Vicarius vRx MCP Server

AI agents call automation_search_all 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.

Why automation_search_all needs a policy

This tool searches and returns automation events without modifying, deleting, or executing actions. The read-only safety enforcement mentioned in the server description reinforces that this API domain operates safely. The 'from' and 'size' parameters confirm it is a standard paginated search returning results, not an operation that changes state.

From the tool's definition Tool name 'automation_search_all' and description 'Returns events' indicate a query/retrieval operation. The POST method with parameters 'q, from, size' are typical of search/pagination operations with no side effects.

Risk signalsBulk/mass operation — affects multiple targets

Questions about automation_search_all

What does the automation_search_all tool do? +

automation \u00b7 POST /automation/searchAll \u2014 Returns events Required: q, from, size. It is categorised as a Read tool in the Vicarius vRx MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on automation_search_all? +

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

automation_search_all is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit automation_search_all? +

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

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

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.