Get the log entries for a specific session.
AI agents call GetSessionLogs 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 data for diagnostic or monitoring purposes. Logs are read-only artifacts that document past events. Unauthorized access to logs could expose sensitive information about backup operations and infrastructure, but the tool itself performs no side effects, creates no resources, and cannot modify or delete data. Therefore, it is classified as a Read operation with low severity risk.
From the tool's definition Tool name is 'GetSessionLogs' and description states 'Get the log entries for a specific session.' The verb 'Get' and the read-only nature of retrieving log entries indicate no data modification, deletion, or execution of operations.
Attacks that exploit this kind of access
Get the log entries for a specific 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 GetSessionLogs: 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.
GetSessionLogs 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 GetSessionLogs 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 GetSessionLogs. 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.
GetSessionLogs 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 →