Get a specific KMS server by ID.
AI agents call GetKMSServer 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 Key Management Server (KMS) configuration by its identifier. It performs no modifications, deletions, or external operations—merely fetching and returning existing data. The blast radius of misuse is minimal; an agent with access could only read KMS server details but cannot change encryption policies, rotate keys, or affect backup operations.
From the tool's definition Tool name 'GetKMSServer' and description 'Get a specific KMS server by ID' indicate a retrieval operation with no side effects. The verb 'Get' and action of retrieving a KMS server configuration by ID is a read-only query.
Attacks that exploit this kind of access
Get a specific KMS server 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 GetKMSServer: 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.
GetKMSServer 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 GetKMSServer 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 GetKMSServer. 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.
GetKMSServer 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 →