get_devserver_statuses
AI agents call get_devserver_statuses to retrieve information from DevServer MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves the status of development servers without modification or side effects. Status queries are inherently read-only operations that pose minimal risk if misused by an AI agent, as they cannot alter system state or trigger external effects. Low severity reflects the informational nature of status monitoring.
From the tool's definition Tool name 'get_devserver_statuses' indicates a status query operation. The server description emphasizes 'monitoring' as a core capability, and this tool fits the read-only pattern alongside other monitoring tools like 'get_devserver_logs' and…
Attacks that exploit this kind of access
get_devserver_statuses. It is categorised as a Read tool in the DevServer MCP MCP Server, which means it retrieves data without modifying state.
Register the DevServer MCP server in PolicyLayer and add a rule for get_devserver_statuses: 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 DevServer MCP. Nothing to install.
get_devserver_statuses 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_devserver_statuses 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_devserver_statuses. 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_devserver_statuses is provided by the DevServer MCP server (uninen/devserver-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 →