AI agents call qf.query.export to retrieve information from Qingflow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and exports query results in a resource-link format. It is fundamentally a data retrieval operation with no side effects or modifications. While it exports data, the export itself is a read-only operation that does not alter the underlying data. The low severity reflects minimal risk even if misused by an agent—it can only retrieve and export existing data.
From the tool's definition Tool name contains 'export' and description states 'Export canonical row queries and return resource links instead of large inline payloads.' The action is querying data and returning links/references to resources, not modifying, deleting, or executing…
Attacks that exploit this kind of access
Export canonical row queries and return resource links instead of large inline payloads. It is categorised as a Read tool in the Qingflow MCP Server, which means it retrieves data without modifying state.
Register the Qingflow MCP server in PolicyLayer and add a rule for qf.query.export: 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 Qingflow. Nothing to install.
qf.query.export 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 qf.query.export 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 qf.query.export. 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.
qf.query.export is provided by the Qingflow MCP server (qingflow-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 →