get_process_status
Get the status of a specific process.
This record as markdown: /tools/intellirecon-console/get-process-status.md
What get_process_status does on Intellirecon Console
AI agents call get_process_status to retrieve information from Intellirecon Console 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 only queries and retrieves the current status of an existing process. It does not start, stop, modify, or execute processes; it merely reads state information. This is a pure Read operation with minimal security risk.
From the tool's definition Tool name and description: 'Get the status of a specific process' — retrieves process information without modification or execution.
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 Intellirecon Console, 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 Intellirecon Console, 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 Intellirecon Console MCP Server, which means it retrieves data without modifying state.
Register the Intellirecon Console 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 Intellirecon Console. 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 Intellirecon Console MCP server (dokotela021/intellirecon-console). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Intellirecon Console, and thousands of servers like it.
This server
Across the catalogue