Gets a specific project by its ID in Dokploy.
AI agents call project-one to retrieve information from Dokploy 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 project information by ID, which is a standard read operation. It does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal—an attacker could only view project details they query. Severity is low because information disclosure alone has limited immediate impact, though confidence is high given the clear retrieval semantics.
From the tool's definition Gets a specific project by its ID in Dokploy. The verb 'Gets' and the action of retrieving a specific project indicate a read-only query operation with no side effects.
Attacks that exploit this kind of access
Gets a specific project by its ID in Dokploy. It is categorised as a Read tool in the Dokploy MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Dokploy MCP Server MCP server in PolicyLayer and add a rule for project-one: 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 Dokploy MCP Server. Nothing to install.
project-one 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 project-one 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 project-one. 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.
project-one is provided by the Dokploy MCP Server MCP server (limehawk/dokploy-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 →