query_paper
AI agents call query_paper to retrieve information from Xiaoya Teacher without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'query_' prefix conventionally indicates a read-only retrieval operation. Given the server's purpose of managing course resources, exams, and classroom data, 'query_paper' almost certainly retrieves paper metadata or content without modifying state. No evidence of side effects, data modification, or privileged operations.
From the tool's definition Tool name 'query_paper' suggests a retrieval operation to fetch paper/exam information. The description is empty, so classification relies on naming convention and context from the 'xiaoya-teacher-mcp-server', which manages educational data including trial…
Attacks that exploit this kind of access
query_paper. It is categorised as a Read tool in the Xiaoya Teacher MCP Server, which means it retrieves data without modifying state.
Register the Xiaoya Teacher MCP server in PolicyLayer and add a rule for query_paper: 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 Xiaoya Teacher. Nothing to install.
query_paper 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 query_paper 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 query_paper. 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.
query_paper is provided by the Xiaoya Teacher MCP server (sav1our520/xiaoya-teacher-mcp-server). 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 →