get_unit_detail

Display detailed telemetry and mutation history for a single fleet unit, including its

SERVERNitrostack SOURCEnitrocloudofficial/nitrostack

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nitrostack/get-unit-detail.md

WHAT IT DOES

What get_unit_detail does on Nitrostack

AI agents call get_unit_detail to retrieve information from Nitrostack without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_unit_detail is rated Low

Tool retrieves and displays historical data without modifying or executing operations.

From the tool's definition Display detailed telemetry and mutation history for a single fleet unit.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_unit_detail safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Nitrostack, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_unit_detail, this is the rule to start with:

get_unit_detail Allowed

get_unit_detail is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_unit_detail": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Nitrostack, apply this rule, and every get_unit_detail call is checked against it from then on.

FAQ

Questions about get_unit_detail

What does the get_unit_detail tool do? +

Display detailed telemetry and mutation history for a single fleet unit, including its. It is categorised as a Read tool in the Nitrostack MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_unit_detail? +

Register the Nitrostack MCP server in PolicyLayer and add a rule for get_unit_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 Nitrostack. Nothing to install.

What risk level is get_unit_detail? +

get_unit_detail is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_unit_detail? +

Yes. Add a rate_limit block to the get_unit_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.

How do I block get_unit_detail completely? +

Set action: deny in the PolicyLayer policy for get_unit_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.

What MCP server provides get_unit_detail? +

get_unit_detail is provided by the Nitrostack MCP server (nitrocloudofficial/nitrostack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Nitrostack, and thousands of servers like it.

This server

All 697 Nitrostack tools →

Across the catalogue

get_torrent_detail on M-Team MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →