Get deployment history for a project
AI agents call get_deployments to retrieve information from Prowpt MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical deployment data from a project, which is a non-destructive query operation. It does not create, modify, delete, or execute any actions—it only fetches and returns information. The blast radius if misused is minimal, as an AI agent could only view deployment history without causing harm.
From the tool's definition Tool name 'get_deployments' and description 'Get deployment history for a project' indicate a retrieval operation with no side effects. The verb 'get' and 'history' are characteristic of read-only queries.
Attacks that exploit this kind of access
Get deployment history for a project. It is categorised as a Read tool in the Prowpt MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Prowpt MCP Server MCP server in PolicyLayer and add a rule for get_deployments: 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 Prowpt MCP Server. Nothing to install.
get_deployments 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_deployments 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_deployments. 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_deployments is provided by the Prowpt MCP Server MCP server (prowptai/prowpt-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 →