List suspicious-process-event detections across the tenant. This is a virtual detection ID that aggregates three real types: Runner-Worker-Memory-Read (credential theft from runner memory), Reverse-Shell, and Privileged-Container. Use for runtime-evidence of compromise during an incident. Every r...
AI agents call list_suspicious_process_events to retrieve information from Stepsecurity without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Even though list_suspicious_process_events only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsBulk/mass operation — affects multiple targets · Admin/system-level operation
Attacks that exploit this kind of access
List suspicious-process-event detections across the tenant. This is a virtual detection ID that aggregates three real types: Runner-Worker-Memory-Read (credential theft from runner memory), Reverse-Shell, and Privileged-Container. Use for runtime-evidence of compromise during an incident. Every result has a. It is categorised as a Read tool in the Stepsecurity MCP Server, which means it retrieves data without modifying state.
Register the Stepsecurity MCP server in PolicyLayer and add a rule for list_suspicious_process_events: 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 Stepsecurity. Nothing to install.
list_suspicious_process_events 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 list_suspicious_process_events 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 list_suspicious_process_events. 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.
list_suspicious_process_events is provided by the Stepsecurity MCP server (step-security/stepsecurity-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.