get_message_event

Get a specific message event by ID with full details

SERVERinstantKOM MCP Server SOURCEinstantkom/mcp-server
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/instantkom-mcp-server/get-message-event.md

What get_message_event does on instantKOM MCP Server

AI agents call get_message_event 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 get_message_event is rated Low

This tool retrieves and queries existing message event data by ID. It performs a lookup operation without creating, modifying, deleting, or executing any actions. The 'get' verb and retrieval-only purpose place it firmly in the Read category. Severity is low because unauthorized reads of message metadata pose minimal immediate harm compared to write, execute, or destructive operations.

From the tool's definition Tool name 'get_message_event' combined with description 'Get a specific message event by ID with full details' indicates a retrieval operation with no side effects. No modification, deletion, or execution capabilities are described.

Questions about get_message_event

What does the get_message_event tool do? +

Get a specific message event by ID with full details. It is categorised as a Read tool in the instantKOM MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_message_event? +

Register the instantKOM MCP Server MCP server in PolicyLayer and add a rule for get_message_event: 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.

What risk level is get_message_event? +

get_message_event is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_message_event? +

Yes. Add a rate_limit block to the get_message_event 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.

How do I block get_message_event completely? +

Set action: deny in the PolicyLayer policy for get_message_event. 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.

What MCP server provides get_message_event? +

get_message_event 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of instantKOM MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.