get_telemetry
Get system telemetry from the API server.
This record as markdown: /tools/nyxstrike/get-telemetry.md
What get_telemetry does on Nyxstrike
AI agents call get_telemetry to retrieve information from Nyxstrike without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_telemetry is rated Low
The tool performs a data retrieval operation ('Get') on system telemetry, which is a read-only action. However, severity is elevated to 'medium' rather than 'low' because in the context of a penetration testing platform (Nyxstrike), telemetry data could expose sensitive system information such as configuration details, performance metrics, or operational state that an attacker could leverage for further exploitation.
From the tool's definition Tool name is 'get_telemetry' and description states 'Get system telemetry from the API server' — this retrieves telemetry data with no modification or destructive capability.
Attacks that exploit this kind of access
The rule that runs get_telemetry safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nyxstrike, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_telemetry, this is the rule to start with:
get_telemetry is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nyxstrike, apply this rule, and every get_telemetry call is checked against it from then on.
Questions about get_telemetry
Get system telemetry from the API server. It is categorised as a Read tool in the Nyxstrike MCP Server, which means it retrieves data without modifying state.
Register the Nyxstrike MCP server in PolicyLayer and add a rule for get_telemetry: 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 Nyxstrike. Nothing to install.
get_telemetry 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_telemetry 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_telemetry. 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_telemetry is provided by the Nyxstrike MCP server (CommonHuman-Lab/nyxstrike). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nyxstrike, and thousands of servers like it.
This server
Across the catalogue