获取用户的历史提问列表，支持时间范围和分页
AI agents call list_questions to retrieve information from KnowS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists historical user questions with filtering and pagination capabilities. It is a query/retrieval operation with no side effects, data modification, or irreversible actions. The medical context (KnowS MCP Server for medical evidence) does not change the fundamental nature of the operation—it remains a read-only data access tool.
From the tool's definition Tool name 'list_questions' and description indicating retrieval of 'user's historical question list' with support for time range and pagination (获取用户的历史提问列表，支持时间范围和分页). No modification, deletion, execution, or financial operations described.
Attacks that exploit this kind of access
获取用户的历史提问列表，支持时间范围和分页. It is categorised as a Read tool in the KnowS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the KnowS MCP Server MCP server in PolicyLayer and add a rule for list_questions: 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 KnowS MCP Server. Nothing to install.
list_questions 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_questions 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_questions. 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_questions is provided by the KnowS MCP Server MCP server (pancrepal-xiaoyibao/mcp-knows-ai). 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 →