list_pages
List the site
This record as markdown: /tools/ai-featureboard-featureboard/list-pages.md
What list_pages does on FeatureBoard
AI agents call list_pages to retrieve information from FeatureBoard without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_pages is rated Low
This tool retrieves and queries page data without any side effects. It performs a simple enumeration of existing pages on the project board, which is a non-destructive read operation. The low severity reflects minimal blast radius—an AI agent listing pages cannot harm data integrity or cause unintended modifications.
From the tool's definition Tool name 'list_pages' combined with description 'List the site' indicates retrieval of page information with no modification capability. The verb 'list' is a classic read operation.
Attacks that exploit this kind of access
The rule that runs list_pages safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FeatureBoard, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_pages, this is the rule to start with:
list_pages is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect FeatureBoard, apply this rule, and every list_pages call is checked against it from then on.
Questions about list_pages
List the site. It is categorised as a Read tool in the FeatureBoard MCP Server, which means it retrieves data without modifying state.
Register the FeatureBoard MCP server in PolicyLayer and add a rule for list_pages: 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 FeatureBoard. Nothing to install.
list_pages 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_pages 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_pages. 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_pages is provided by the FeatureBoard MCP server (https://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FeatureBoard, and thousands of servers like it.
This server
Across the catalogue