List sections in a Pages document with preview text and word counts.
AI agents call pages.list_sections to retrieve information from Orchard without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries structural information (sections, preview text, word counts) from a Pages document. It performs no modifications, deletions, or side effects. It is a straightforward read operation analogous to the sibling tools 'calendar.list_calendars', 'calendar.list_events', and 'contacts.list_groups' also present on this server.
From the tool's definition Tool name 'list_sections' and description 'List sections in a Pages document with preview text and word counts' indicates retrieval of document metadata without modification.
Documented attack patterns abuse exactly the kind of access pages.list_sections gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Orchard, and nothing reaches the server without passing your rules. This is the rule we recommend for pages.list_sections:
{
"version": "1",
"default": "deny",
"tools": {
"pages.list_sections": {}
}
}pages.list_sections is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List sections in a Pages document with preview text and word counts. It is categorised as a Read tool in the Orchard MCP Server, which means it retrieves data without modifying state.
Register the Orchard MCP server in PolicyLayer and add a rule for pages.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 Orchard. Nothing to install.
pages.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 pages.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 pages.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.
pages.list_sections is provided by the Orchard MCP server (l22-io/orchard-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Orchard, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
65 Orchard tools catalogued and risk-classified — across an index of 43,000+ MCP servers.