AI agents call flowise_list_document_stores to retrieve information from Flowise without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and enumerates existing document store configurations without creating, modifying, deleting, or executing any operations. It is a straightforward read-only query, posing minimal security risk unless the document store metadata itself contains sensitive information that should not be exposed.
From the tool's definition The tool 'flowise_list_document_stores' with description 'List all document stores configured in Flowise' performs a retrieval/query operation (list) with no side effects on the data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List all document stores configured in Flowise. It is categorised as a Read tool in the Flowise MCP Server, which means it retrieves data without modifying state.
Register the Flowise MCP server in PolicyLayer and add a rule for flowise_list_document_stores: 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 Flowise. Nothing to install.
flowise_list_document_stores 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 flowise_list_document_stores 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 flowise_list_document_stores. 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.
flowise_list_document_stores is provided by the Flowise MCP server (julidir/flowise-mcp). 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 →