Lists all Macroforge documentation sections. Returns sections with: - title: Section name - use_cases: When this doc is useful (comma-separated keywords) - path: File path - category: Category name WORKFLOW: 1. Call list-sections FIRST for any Macroforge-related task 2. Analyze use_cases to find ...
AI agents call list-sections to retrieve information from Macroforge 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 query operation that retrieves and returns documentation section information. There is no data modification, code execution, deletion, or financial impact. It is a straightforward informational lookup with no reversible or irreversible side effects, making it a Read category tool with low severity.
From the tool's definition Tool description explicitly states it 'Lists all Macroforge documentation sections' and returns metadata (title, use_cases, path, category). The verb 'lists' and return of read-only documentation metadata confirm retrieval-only behavior with no side effects.
Attacks that exploit this kind of access
Lists all Macroforge documentation sections. Returns sections with: - title: Section name - use_cases: When this doc is useful (comma-separated keywords) - path: File path - category: Category name WORKFLOW: 1. Call list-sections FIRST for any Macroforge-related task 2. Analyze use_cases to find relevant sections 3. Call get-documentation with ALL relevant section names Example use_cases:. It is categorised as a Read tool in the Macroforge MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Macroforge 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 Macroforge 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 Macroforge MCP Server MCP server (macroforge-ts/mcp-server). 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 →