Get a specific task session by ID.
AI agents call GetTaskSession 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 retrieves information about a task session without modifying, executing, or deleting any data. It is a straightforward query operation that poses minimal risk if called by an AI agent, as it only returns existing data about backup/replication task sessions. Low severity is appropriate for passive information retrieval in a backup management context.
From the tool's definition Tool name 'GetTaskSession' and description 'Get a specific task session by ID' indicate a retrieval operation with no side effects. The verb 'Get' and lack of any modification language (create, update, delete, execute) confirm read-only semantics.
Attacks that exploit this kind of access
Get a specific task session by ID. 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 GetTaskSession: 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.
GetTaskSession 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 GetTaskSession 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 GetTaskSession. 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.
GetTaskSession 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 →