get_process_status

Get the status of a specific process.

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-process-status.md

What get_process_status does on Nyxstrike

AI agents call get_process_status 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_process_status is rated Low

This tool retrieves process status information only. It has no side effects, does not modify data, execute code, or perform destructive actions. Despite the server's offensive security context, this specific tool is a simple read-only query that returns process state information. Severity is low because the blast radius of accidental misuse is minimal—querying process status cannot harm systems or data.

From the tool's definition Tool name 'get_process_status' and description 'Get the status of a specific process' indicate a query operation that retrieves information without modifying or executing anything.

Questions about get_process_status

What does the get_process_status tool do? +

Get the status of a specific process. 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_process_status? +

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

What risk level is get_process_status? +

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

Can I rate-limit get_process_status? +

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

How do I block get_process_status completely? +

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

What MCP server provides get_process_status? +

get_process_status 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.