read_chat
Read chat details including participants and last update time by chat ID.
This record as markdown: /tools/heznpc-airmcp/read-chat.md
What read_chat does on AirMCP
AI agents call read_chat to retrieve information from AirMCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why read_chat is rated Low
This tool retrieves existing chat metadata (participants, last update time) without creating, modifying, deleting, or executing any operations. It is a straightforward data query with no side effects, fitting the Read category. Severity is low because exposure of chat metadata alone poses minimal risk compared to reading message content or allowing modifications.
From the tool's definition Tool name is 'read_chat' and description states it reads chat details including participants and last update time. The verb 'read' and the retrieval-only nature (no modification or side effects mentioned) clearly indicate a read operation.
Attacks that exploit this kind of access
The rule that runs read_chat safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AirMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For read_chat, this is the rule to start with:
read_chat 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 AirMCP, apply this rule, and every read_chat call is checked against it from then on.
Questions about read_chat
Read chat details including participants and last update time by chat ID. It is categorised as a Read tool in the AirMCP MCP Server, which means it retrieves data without modifying state.
Register the Air MCP server in PolicyLayer and add a rule for read_chat: 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 AirMCP. Nothing to install.
read_chat 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 read_chat 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 read_chat. 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.
read_chat is provided by the Air MCP server (airmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Air, and thousands of servers like it.
This server
Across the catalogue