List all available Equinox documentation sections.
AI agents call list-sections to retrieve information from Equinox MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple enumeration/listing of documentation sections, which is a read-only operation that retrieves metadata about available resources. There is no risk of data modification, code execution, or destructive actions. The blast radius of misuse is minimal—an agent could only discover what sections exist in the documentation.
From the tool's definition Tool name 'list-sections' and description 'List all available Equinox documentation sections' indicate a retrieval operation with no side effects. It queries available documentation structure without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
List all available Equinox documentation sections. It is categorised as a Read tool in the Equinox MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Equinox MCP Server MCP server in PolicyLayer and add a rule for list-sections: 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 Equinox MCP Server. Nothing to install.
list-sections 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 list-sections 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 list-sections. 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.
list-sections is provided by the Equinox MCP Server MCP server (s27183/equinox-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 →