Check deployment status for the current project using .ploi.json config
AI agents call get_project_deploy_status to retrieve information from Ploi MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads/checks deployment status from the .ploi.json config file. It has no side effects, does not execute deployments, create resources, delete data, or commit financial transactions. It is purely informational, making it a Read category tool with low severity.
From the tool's definition Tool name 'get_project_deploy_status' and description 'Check deployment status' indicate a query operation that retrieves status information without modifying or executing deployment actions.
Attacks that exploit this kind of access
Check deployment status for the current project using .ploi.json config. It is categorised as a Read tool in the Ploi MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Ploi MCP Server MCP server in PolicyLayer and add a rule for get_project_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 Ploi MCP Server. Nothing to install.
get_project_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_project_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_project_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_project_deploy_status is provided by the Ploi MCP Server MCP server (sudanese/ploi-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 →