submit_student_mark
AI agents use submit_student_mark to create or update resources in Xiaoya Teacher — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Xiaoya Teacher environment.
This tool creates or modifies student assessment data (marks/grades), which are critical educational records. While it doesn't delete data (not Destructive) or execute arbitrary code (not Execute), it does reversibly change persistent student information. The high severity reflects the blast radius of erroneous grade submissions affecting student records, academic standing, and transcripts. Confidence is moderate (0.
From the tool's definition Tool name 'submit_student_mark' indicates modification of student grades/marks, which are educational records. No description provided to clarify exact behavior.
Attacks that exploit this kind of access
submit_student_mark. It is categorised as a Write tool in the Xiaoya Teacher MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Xiaoya Teacher MCP server in PolicyLayer and add a rule for submit_student_mark: 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.
submit_student_mark is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the submit_student_mark 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 submit_student_mark. 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.
submit_student_mark 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 →