AI agents call qf.query.record 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 a single record from the Qingflow system using a query interface. It performs a read-only operation that queries and returns data without creating, modifying, or deleting anything. The 'query handle' return suggests it is designed for data inspection rather than operational side effects. No destructive, financial, or code-execution semantics are present.
From the tool's definition Tool description states 'Fetch one record' and 'return a query handle' — retrieval operation with no modification capability. The verb 'Fetch' and context of returning a query handle (for inspection/analysis) indicate data retrieval only.
Attacks that exploit this kind of access
Fetch one record through the canonical DSL and return a query handle. 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.record: 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.record 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.record 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.record. 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.record 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 →