AI agents call get_deploy_status 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 is a read-only query tool that retrieves status information about an existing deployment. It has no capability to modify, delete, or execute operations—it simply returns state information for observability. The low severity reflects that misuse would only expose status data, not cause operational changes.
From the tool's definition Tool name is 'get_deploy_status' and description states it checks the current deployment status and 'Returns the app'. The verb 'get' and 'check' indicate data retrieval. The description explicitly frames this as monitoring, with no side effects mentioned.
Attacks that exploit this kind of access
Check the current deployment status of an app. Use this after deploying to monitor build progress. Returns 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 get_deploy_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 Myvtp. Nothing to install.
get_deploy_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 get_deploy_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 get_deploy_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.
get_deploy_status 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 →