list_message_events
List message delivery and interaction events with optional filters. Tracks sent, delivered, read, clicked, received, and queued states.
This record as markdown: /tools/instantkom-mcp-server/list-message-events.md
What list_message_events does on instantKOM MCP Server
AI agents call list_message_events to retrieve information from instantKOM MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_message_events is rated Low
This tool queries and retrieves historical message delivery and interaction event data. It has no side effects, does not create or modify data, does not execute code or trigger external operations, and does not delete or move resources. The function is purely informational/observational, consistent with the Read category (retrieve, query, list, fetch).
From the tool's definition Tool name 'list_message_events' and description explicitly states it 'List[s]' events with 'optional filters' and 'Tracks' states—purely a retrieval operation with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
The rule that runs list_message_events safely
PolicyLayer is an MCP gateway: it sits between your AI agents and instantKOM MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_message_events, this is the rule to start with:
list_message_events 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 instantKOM MCP Server, apply this rule, and every list_message_events call is checked against it from then on.
Questions about list_message_events
List message delivery and interaction events with optional filters. Tracks sent, delivered, read, clicked, received, and queued states. It is categorised as a Read tool in the instantKOM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the instantKOM MCP Server MCP server in PolicyLayer and add a rule for list_message_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 instantKOM MCP Server. Nothing to install.
list_message_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_message_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_message_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_message_events is provided by the instantKOM MCP Server MCP server (instantkom/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on instantKOM MCP Server, and thousands of servers like it.
This server
Across the catalogue