Get recent release history. Check for changes relevant to your task.
AI agents call get-changelog 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 tool retrieves and queries changelog or release history data without creating, modifying, executing operations, or deleting anything. It is a pure information retrieval operation with no side effects, placing it firmly in the Read category. The low severity reflects minimal risk: changelog data is typically non-sensitive, and misuse would only return informational content without operational impact.
From the tool's definition Tool name 'get-changelog' and description 'Get recent release history. Check for changes relevant to your task.' indicate a read-only retrieval of historical version/release information.
Attacks that exploit this kind of access
Get recent release history. Check for changes relevant to your task. 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-changelog: 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-changelog 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-changelog 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-changelog. 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-changelog 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 →