AI agents call vunet_list_data_models to retrieve information from Vunet without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns available data model definitions from a multi-tenant observability platform. It performs no side effects, does not execute code, does not modify data, and does not access sensitive operational metrics — only schema metadata. The blast radius of misuse is minimal since listing available models does not expose raw data, execute operations, or cause state changes.
From the tool's definition Tool name contains 'list' and description states 'List common Vunet data models' — a retrieval operation with no modification or execution capability. Returns schema/metadata information only.
Attacks that exploit this kind of access
List common Vunet data models organized by category (APM, Infrastructure, Database, Network, etc.). It is categorised as a Read tool in the Vunet MCP Server, which means it retrieves data without modifying state.
Register the Vunet MCP server in PolicyLayer and add a rule for vunet_list_data_models: 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 Vunet. Nothing to install.
vunet_list_data_models 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 vunet_list_data_models 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 vunet_list_data_models. 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.
vunet_list_data_models is provided by the Vunet MCP server (mithung-vunet/vunet-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 →