AI agents call flowise_get_document_store 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 retrieves and queries information about a document store. The verb 'get' and absence of any modification language (create, update, delete) confirm this is a read-only operation with no side effects. The severity is low because retrieving metadata about a document store presents minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'flowise_get_document_store' and description 'Get detailed information about a specific document store' indicate retrieval of existing data without modification.
Attacks that exploit this kind of access
Get detailed information about a specific document store. 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_get_document_store: 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_get_document_store 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_get_document_store 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_get_document_store. 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_get_document_store 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 →