AI agents call dokploy_get_app_monitoring to retrieve information from Dokploy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves application monitoring metrics (CPU and memory usage). It performs a read-only operation that returns observational data about system state with no capability to modify, create, delete, or execute operations. The minimal blast radius of exposing this tool is that an agent could gain visibility into application performance metrics, which is informational only.
From the tool's definition Tool name contains 'get_app_monitoring' and description states 'Get CPU and memory metrics for an application by its appName' — purely retrieves monitoring data without modification or side effects.
Attacks that exploit this kind of access
Get CPU and memory metrics for an application by its appName. It is categorised as a Read tool in the Dokploy MCP Server, which means it retrieves data without modifying state.
Register the Dokploy MCP server in PolicyLayer and add a rule for dokploy_get_app_monitoring: 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. Nothing to install.
dokploy_get_app_monitoring 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 dokploy_get_app_monitoring 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 dokploy_get_app_monitoring. 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.
dokploy_get_app_monitoring is provided by the Dokploy MCP server (wyattjoh/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 →