AI agents call get_app_config 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 queries and returns existing deployment configuration data from the VTP platform without modifying, deleting, or executing any operations. It is purely informational—reading app configuration metadata (connections, volumes, etc.). No reversible or irreversible changes occur, no code execution is triggered, and no financial operations are involved.
From the tool's definition The tool description explicitly states it 'retrieves the config used in the previous deployment' and is used 'when redeploying an app that exists but has no local vtp.yaml'. The verb 'get' and 'retrieves' indicate a query/read operation with no side effects.
Attacks that exploit this kind of access
Get the deployment configuration for an existing app. Use this when redeploying an app that exists but has no local vtp.yaml - retrieves the config used in the previous deployment (connections, volumes, etc.). 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 get_app_config: 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.
get_app_config 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_app_config 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_app_config. 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_app_config 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.
get_app_config is one line of Myvtp's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →