get_process_status
Get the status of a specific process.
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.
Attacks that exploit this kind of access
The rule that runs get_process_status 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_process_status, this is the rule to start with:
get_process_status 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_process_status call is checked against it from then on.
Questions about get_process_status
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.
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.
get_process_status 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_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.
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.
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.
This server
Across the catalogue