list_sources
List a board
This record as markdown: /tools/ai-featureboard-featureboard/list-sources.md
What list_sources does on FeatureBoard
AI agents call list_sources 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_sources is rated Low
This tool retrieves or queries board data without modifying, deleting, or executing external operations. The 'list' operation is a standard read pattern. Severity is low because listing board contents has minimal blast radius—it only exposes existing information without causing harm if queried repeatedly or inappropriately.
From the tool's definition Tool name 'list_sources' and description 'List a board' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs list_sources 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_sources, this is the rule to start with:
list_sources 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_sources call is checked against it from then on.
Questions about list_sources
List a board. 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_sources: 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_sources 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_sources 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_sources. 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_sources 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