查询课程组的全部签到记录情况
AI agents call query_attendance_records 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.
This tool retrieves and reads attendance records for a course group. It performs no modifications, deletions, or side effects. It is a straightforward data query operation with minimal security risk—even if misused, an AI agent could only view existing attendance data, not alter it or affect other systems.
From the tool's definition Tool name contains '查询' (query) and description states '查询...签到记录情况' (query attendance records). The verb 'query' and absence of modification language (create, update, delete) indicate data retrieval only.
Attacks that exploit this kind of access
查询课程组的全部签到记录情况. 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_attendance_records: 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_attendance_records 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_attendance_records 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_attendance_records. 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_attendance_records 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 →