Get configuration for a basin.
AI agents call get_basin_config 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 retrieves configuration data for a basin without modifying, deleting, or executing any operations. It is a straightforward query operation that returns information about an existing basin. The blast radius is minimal as it only exposes configuration metadata without capability to change state or perform actions.
From the tool's definition Tool name 'get_basin_config' and description 'Get configuration for a basin' indicate a retrieval operation with no side effects. 'Get' is characteristic of Read operations.
Attacks that exploit this kind of access
Get configuration for a basin. 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 get_basin_config: 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.
get_basin_config 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_basin_config 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_basin_config. 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_basin_config 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.
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 →