See who has read up to a given message (or the latest). Useful to check if
AI agents call read_receipts to retrieve information from Claude Team MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about message consumption within a team collaboration system. It performs a query operation to determine which team members have read specific messages, with no capability to modify, delete, or execute actions. The blast radius of misuse is minimal—an agent gaining visibility into team member activity patterns poses no direct operational risk.
From the tool's definition Tool name 'read_receipts' and description 'See who has read up to a given message (or the latest)' indicate a retrieval-only operation that queries message read status without modification or side effects.
Attacks that exploit this kind of access
See who has read up to a given message (or the latest). Useful to check if. It is categorised as a Read tool in the Claude Team MCP MCP Server, which means it retrieves data without modifying state.
Register the Claude Team MCP server in PolicyLayer and add a rule for read_receipts: 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 Claude Team MCP. Nothing to install.
read_receipts 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_receipts 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_receipts. 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_receipts is provided by the Claude Team MCP server (lakshan12367/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 →