AI agents call list_supported_connections to retrieve information from Myvtp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays available API connections configured on the VTP platform. It performs no write operations, does not execute code or trigger external actions, and does not delete or move resources. The blast radius of misuse is minimal—worst case, an AI agent learns what integrations are available, which is low-sensitivity enumeration. Classified as Read.
From the tool's definition Tool name 'list_supported_connections' and description 'List available third-party API connections' explicitly indicate a read-only query operation. The description states it lists available connections without modification or execution.
Attacks that exploit this kind of access
List available third-party API connections (OpenAI, Anthropic, etc.). Call this during code analysis if the app imports any third-party SDK or references API keys. Cross-reference the app. It is categorised as a Read tool in the Myvtp MCP Server, which means it retrieves data without modifying state.
Register the Myvtp MCP server in PolicyLayer and add a rule for list_supported_connections: 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 Myvtp. Nothing to install.
list_supported_connections 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 list_supported_connections 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 list_supported_connections. 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.
list_supported_connections is provided by the Myvtp MCP server (myvtp/mcp). 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 →