get_telemetry

Get system telemetry from the API server.

SERVERNyxstrike SOURCECommonHuman-Lab/nyxstrike
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/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.

Questions about get_telemetry

What does the get_telemetry tool do? +

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.

How do I enforce a policy on get_telemetry? +

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.

What risk level is get_telemetry? +

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

Can I rate-limit get_telemetry? +

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.

How do I block get_telemetry completely? +

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.

What MCP server provides get_telemetry? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Nyxstrike's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.