Get GPU status and availability (NVIDIA and AMD)
AI agents call get_gpu_status to retrieve information from MCP Developer Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries GPU status information (NVIDIA and AMD availability), which is a passive data retrieval operation with no side effects, no code execution, and no state changes. It belongs in the Read category with low severity since misconfiguration poses minimal risk—an AI agent using this tool would only be able to view GPU availability metrics, not allocate resources or execute code.
From the tool's definition Tool name 'get_gpu_status' and description 'Get GPU status and availability' indicate a read-only query operation that retrieves system information without modifying or executing anything.
Attacks that exploit this kind of access
Get GPU status and availability (NVIDIA and AMD). It is categorised as a Read tool in the MCP Developer Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Developer Server MCP server in PolicyLayer and add a rule for get_gpu_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 MCP Developer Server. Nothing to install.
get_gpu_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_gpu_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_gpu_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_gpu_status is provided by the MCP Developer Server MCP server (ra86-dev/mcpdev-server). 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 →