Read a site
AI agents call get_deploy_script 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 retrieves information about a deployment script for a site, which is a read-only operation with no side effects. It falls clearly into the Read category. Severity is low because reading deployment scripts poses minimal direct risk—the information retrieved is typically non-sensitive build/deployment metadata, and there are no destructive, financial, or execution side effects.
From the tool's definition Tool description explicitly states: "Read a site". The tool name "get_deploy_script" and context within a deployment management system indicates it retrieves deployment script content without modifying state.
Attacks that exploit this kind of access
Read a site. 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_deploy_script: 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_deploy_script 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_script 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_script. 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_script 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 →