Get logs for a SureBackup scan task session.
AI agents call GetScanSessionLog 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 historical log information from a completed SureBackup scan session. It performs a query/fetch operation on read-only data without side effects. While logs may contain sensitive information (lowering severity slightly), the action itself is passive retrieval. The blast radius if misused is limited to information disclosure rather than operational impact.
From the tool's definition Tool name 'GetScanSessionLog' and description 'Get logs for a SureBackup scan task session' indicate retrieval of existing log data with no modification, creation, or deletion of data.
Attacks that exploit this kind of access
Get logs for a SureBackup scan task session. 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 GetScanSessionLog: 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.
GetScanSessionLog 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 GetScanSessionLog 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 GetScanSessionLog. 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.
GetScanSessionLog 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 →