get_user_instance_detail
AI agents call get_user_instance_detail to retrieve information from Nebulablock without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool fetches information about a user's GPU instance(s), consistent with the pattern of other 'get_' prefixed tools on this server (get_computing_products, get_user_credit_balance, get_user_instances). No modification, deletion, or execution occurs. The blast radius of retrieving instance metadata is low.
From the tool's definition Tool name 'get_user_instance_detail' combined with sibling tools showing create/delete/get patterns indicates this retrieves instance details. The 'get_' prefix and 'detail' suffix are characteristic of read operations.
Attacks that exploit this kind of access
get_user_instance_detail. It is categorised as a Read tool in the Nebulablock MCP Server, which means it retrieves data without modifying state.
Register the Nebulablock MCP server in PolicyLayer and add a rule for get_user_instance_detail: 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 Nebulablock. Nothing to install.
get_user_instance_detail 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_user_instance_detail 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_user_instance_detail. 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_user_instance_detail is provided by the Nebulablock MCP server (nebula-block-data/nebulablock-mcp-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 →