Get the current status of the monitored development server
AI agents call get_dev_server_status 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.
This tool retrieves status information about a development server. It performs no state changes, does not execute commands, and does not delete or modify data. It is a straightforward read operation with minimal risk—even if misused by an agent, it only exposes the server's current state without enabling harmful actions. The low severity reflects the limited blast radius of status information disclosure.
From the tool's definition Tool name 'get_dev_server_status' and description 'Get the current status of the monitored development server' indicate a query operation that retrieves information without modification or side effects.
Documented attack patterns abuse exactly the kind of access get_dev_server_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DevServer MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_dev_server_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_dev_server_status": {}
}
}get_dev_server_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the current status of the monitored development server. 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_dev_server_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 DevServer MCP. Nothing to install.
get_dev_server_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_dev_server_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_dev_server_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_dev_server_status is provided by the DevServer MCP server (mntlabs/devserver-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from DevServer MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 DevServer MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.