Get server version, available tools, and metadata. Call on first use to check for updates.
AI agents call get-server-info to retrieve information from Vcluster Yaml without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a simple informational query tool that retrieves metadata about the server itself. It returns read-only information (version, available tools, metadata) with no capability to modify, execute, or delete anything. The typical use case of 'check for updates' is also a passive read operation. Blast radius is minimal as misuse cannot compromise data or trigger unintended operations.
From the tool's definition Tool name 'get-server-info' and description 'Get server version, available tools, and metadata' indicates retrieval of static server information without side effects.
Attacks that exploit this kind of access
Get server version, available tools, and metadata. Call on first use to check for updates. It is categorised as a Read tool in the Vcluster Yaml MCP Server, which means it retrieves data without modifying state.
Register the Vcluster Yaml MCP server in PolicyLayer and add a rule for get-server-info: 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 Vcluster Yaml. Nothing to install.
get-server-info 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 get-server-info 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 get-server-info. 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.
get-server-info is provided by the Vcluster Yaml MCP server (vcluster-yaml-mcp-server). 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 →