Read records from a stream. Specify a starting point with seq_num, timestamp, or tail_offset.
AI agents call read_records to retrieve information from S2 StreamStore MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing data from a stream using parameters like seq_num, timestamp, or tail_offset to specify the starting point. It has no capacity to modify, delete, or execute external operations. It is a straightforward read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name is 'read_records' and description states 'Read records from a stream.' The operation retrieves data without modification or side effects.
Attacks that exploit this kind of access
Read records from a stream. Specify a starting point with seq_num, timestamp, or tail_offset. It is categorised as a Read tool in the S2 StreamStore MCP Server MCP Server, which means it retrieves data without modifying state.
Register the S2 StreamStore MCP Server MCP server in PolicyLayer and add a rule for read_records: 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 S2 StreamStore MCP Server. Nothing to install.
read_records 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_records 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_records. 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_records is provided by the S2 StreamStore MCP Server MCP server (s2-streamstore/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
read_records is one line of S2 StreamStore MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →