Get all automation import/export sessions.
AI agents call GetAllAutomationSessions to retrieve information from Veeam VBR v13 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves information about automation import/export sessions without creating, modifying, deleting, or executing any operations. It is a straightforward data retrieval function with no side effects, fitting the Read category. The severity is low as it only exposes metadata about sessions with no blast radius beyond information disclosure.
From the tool's definition Tool name 'GetAllAutomationSessions' and description 'Get all automation import/export sessions' indicate a retrieval operation with the verb 'Get' and no modification or destructive action.
Attacks that exploit this kind of access
Get all automation import/export sessions. It is categorised as a Read tool in the Veeam VBR v13 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Veeam VBR v13 MCP Server MCP server in PolicyLayer and add a rule for GetAllAutomationSessions: 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 Veeam VBR v13 MCP Server. Nothing to install.
GetAllAutomationSessions 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 GetAllAutomationSessions 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 GetAllAutomationSessions. 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.
GetAllAutomationSessions is provided by the Veeam VBR v13 MCP Server MCP server (kid-boy/veeam-mcp-13). 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 →