Fetch the actual live DataModels (signals) configured in this VuNet tenant by calling /api/vuaccel/datamodel/. Returns real signal names, types (Metric/Event/Log), data sources, and column details. Use this to discover what data is available before querying with vunet_query_metric.
AI agents call vunet_fetch_datamodels 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 is a data discovery and querying tool that retrieves metadata about available data models from the Vunet observability platform. It has read-only semantics with no capability to modify state, execute code, delete data, or perform financial operations. The blast radius of misuse is minimal—an AI agent could only enumerate available signals, which is informational.
From the tool's definition Tool description states it 'Fetch[es] the actual live DataModels' and 'Returns real signal names, types, data sources, and column details.' The action is retrieval/discovery with 'no side effects' - it queries an API endpoint (/api/vuaccel/datamodel/) to list…
Attacks that exploit this kind of access
Fetch the actual live DataModels (signals) configured in this VuNet tenant by calling /api/vuaccel/datamodel/. Returns real signal names, types (Metric/Event/Log), data sources, and column details. Use this to discover what data is available before querying with vunet_query_metric. 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_fetch_datamodels: 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_fetch_datamodels 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_fetch_datamodels 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_fetch_datamodels. 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_fetch_datamodels 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 →