获取ddnet进程状态
AI agents call get_ddnet_game_status to retrieve information from DDNet 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 process status information with no side effects. It performs a simple state query of a running game process, which is a classic Read operation. The low severity reflects minimal risk—an AI agent misusing this to spam status checks causes only performance concerns, not data loss or unauthorized changes.
From the tool's definition Tool name 'get_ddnet_game_status' and description '获取ddnet进程状态' (retrieve/get DDNet process status) indicate a read-only query operation that retrieves the current state of a game process without modifying anything.
Attacks that exploit this kind of access
获取ddnet进程状态. It is categorised as a Read tool in the DDNet MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DDNet MCP Server MCP server in PolicyLayer and add a rule for get_ddnet_game_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 DDNet MCP Server. Nothing to install.
get_ddnet_game_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_ddnet_game_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_ddnet_game_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_ddnet_game_status is provided by the DDNet MCP Server MCP server (silverhi/ddnet-mcpserver). 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 →