list_qa_questions
Use this to read the diligence Q&A queue when prioritising what to answer next or auditing open questions. Optional status filter (open|in_progress|answered|closed). Returns title, asker, priority, due_date.
This record as markdown: /tools/8vdx1-fundos-mcp/list-qa-questions.md
What list_qa_questions does on Fundos
AI agents call list_qa_questions to retrieve information from Fundos without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_qa_questions is rated Low
This tool queries and lists Q&A queue items with metadata. It has no side effects, cannot modify data, execute operations, or affect financial positions. The optional status filter is a read-only query parameter. Severity is low because misuse would only expose information already known to authorized fund staff; there is no blast radius of destructive or financial consequence.
From the tool's definition Tool description states 'read the diligence Q&A queue' and 'Returns title, asker, priority, due_date' — purely retrieval of existing data with optional filtering. No modification, execution, deletion, or financial transaction occurs.
Attacks that exploit this kind of access
The rule that runs list_qa_questions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Fundos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_qa_questions, this is the rule to start with:
list_qa_questions 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 Fundos, apply this rule, and every list_qa_questions call is checked against it from then on.
Questions about list_qa_questions
Use this to read the diligence Q&A queue when prioritising what to answer next or auditing open questions. Optional status filter (open|in_progress|answered|closed). Returns title, asker, priority, due_date. It is categorised as a Read tool in the Fundos MCP Server, which means it retrieves data without modifying state.
Register the Fundos MCP server in PolicyLayer and add a rule for list_qa_questions: 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 Fundos. Nothing to install.
list_qa_questions 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_qa_questions 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_qa_questions. 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_qa_questions is provided by the Fundos MCP server (8vdx1/fundos-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Fundos, and thousands of servers like it.
This server
Across the catalogue