Get events for a specific message
AI agents call get_events_for_message to retrieve information from Dust MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical events associated with a message without modifying, creating, deleting, or executing any operations. It is a straightforward data retrieval function consistent with the Read category. The low severity reflects minimal risk—unauthorized access could expose message event history, but causes no data loss or execution of commands.
From the tool's definition Tool name 'get_events_for_message' and description 'Get events for a specific message' indicate a retrieval operation with no side effects. The verb 'get' and the context of retrieving message events confirm this is a read-only query.
Attacks that exploit this kind of access
Get events for a specific message. It is categorised as a Read tool in the Dust MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Dust MCP Server MCP server in PolicyLayer and add a rule for get_events_for_message: 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 Dust MCP Server. Nothing to install.
get_events_for_message 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_events_for_message 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_events_for_message. 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_events_for_message is provided by the Dust MCP Server MCP server (ma3u/dust-mcp-server-postman-railway). 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 →