Get Google Cloud authentication information.
AI agents call RequestAuthentication 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 authentication information, which is fundamentally a Read operation (query/fetch). However, severity is high because exposure of authentication credentials to an unauthorized or compromised AI agent could enable lateral movement, unauthorized access to cloud resources, and privilege escalation across the Veeam infrastructure and connected Google Cloud environments.
From the tool's definition Tool name 'RequestAuthentication' and description 'Get Google Cloud authentication information' indicate retrieval of authentication credentials or tokens without modification.
Attacks that exploit this kind of access
Get Google Cloud authentication information. 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 RequestAuthentication: 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.
RequestAuthentication 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 RequestAuthentication 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 RequestAuthentication. 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.
RequestAuthentication 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 →