AI agents call vunet_get_status 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 performs a read-only operation to retrieve connection status and tenant information from the Vunet observability platform. It has no side effects, does not execute code, does not modify data, and does not involve financial transactions. The blast radius of misuse is minimal—an attacker could only gain visibility into connection state and tenant metadata, which is already known to any authenticated user.
From the tool's definition Tool name 'vunet_get_status' and description 'Get the current connection status and tenant information' indicate a query operation that retrieves status and metadata without modifying, executing, or deleting data.
Attacks that exploit this kind of access
Get the current connection status and tenant information. 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_get_status: 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_get_status 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_get_status 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_get_status. 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_get_status 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 →