AI agents call list_documents to retrieve information from Qtz Iris without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | 最大返回数量，默认 100 |
filter | string | — | 文件过滤模式，如 *.cls |
Parameters from the server's own tool schema.
This tool queries and lists documents within a namespace, which is a read-only operation that retrieves data without side effects. The description explicitly indicates listing/enumeration functionality rather than creation, modification, deletion, or execution of operations.
From the tool's definition Tool name 'list_documents' and description '列出命名空间中的文档' (list documents in namespace) indicate a retrieval operation with no modification capability.
Attacks that exploit this kind of access
列出命名空间中的文档. It is categorised as a Read tool in the Qtz Iris MCP Server, which means it retrieves data without modifying state.
list_documents accepts 2 parameters: limit, filter. The full parameter table on this page comes from the server's own tool schema.
Register the Qtz Iris MCP server in PolicyLayer and add a rule for list_documents: 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 Qtz Iris. Nothing to install.
list_documents 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_documents 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_documents. 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_documents is provided by the Qtz Iris MCP server (qtz-iris-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 →