List recent detected events (may be empty). Supports monitor_id + limit (max 50).
AI agents call list_recent_events to retrieve information from Parallel-Poke MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries historical event data; it causes no side effects, does not modify state, and does not execute external operations. The maximum result limit (50) further constrains the blast radius. Classified as Read with low severity since exposure poses minimal risk—an attacker could only observe past monitor events, not alter monitors or trigger actions.
From the tool's definition list_recent_events retrieves and displays 'recent detected events' with parameters for filtering (monitor_id, limit). The words 'list' and 'detected events' indicate a query/retrieval operation with no data modification or execution capability.
Attacks that exploit this kind of access
List recent detected events (may be empty). Supports monitor_id + limit (max 50). It is categorised as a Read tool in the Parallel-Poke MCP MCP Server, which means it retrieves data without modifying state.
Register the Parallel-Poke MCP server in PolicyLayer and add a rule for list_recent_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 Parallel-Poke MCP. Nothing to install.
list_recent_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_recent_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_recent_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_recent_events is provided by the Parallel-Poke MCP server (konarkm/parallel-poke-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →