Get list of segment IDs within proximity constraint.
AI agents call get_adjacent_segments to retrieve information from BigContext MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists segment IDs based on a proximity constraint—a pure query operation with no side effects. It fits the Read category definition: retrieves or queries data without modifying state. The low severity reflects that misuse would only expose document structure/metadata, not enable destructive, financial, or code execution risks.
From the tool's definition Tool name 'get_adjacent_segments' and description 'Get list of segment IDs within proximity constraint' indicate a retrieval operation that returns segment identifiers without modifying, deleting, or executing any operations.
Attacks that exploit this kind of access
Get list of segment IDs within proximity constraint. It is categorised as a Read tool in the BigContext MCP MCP Server, which means it retrieves data without modifying state.
Register the BigContext MCP server in PolicyLayer and add a rule for get_adjacent_segments: 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 BigContext MCP. Nothing to install.
get_adjacent_segments 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_adjacent_segments 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_adjacent_segments. 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_adjacent_segments is provided by the BigContext MCP server (rixmerz/bigcontext_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 →