create_course_resource
AI agents use create_course_resource 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.
Based on the tool name and sibling tools (batch_create_questions, configure_paper_basics, create_answer_item, etc.) which are clearly Write operations, this tool almost certainly creates new course resource entries. Write operations are reversible and modify data without irreversible deletion.
From the tool's definition Tool named 'create_course_resource' with no description provided. Naming convention and context (educational platform for teachers managing course resources) indicate it creates/adds new resources.
Attacks that exploit this kind of access
create_course_resource. 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 create_course_resource: 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.
create_course_resource 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 create_course_resource 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 create_course_resource. 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.
create_course_resource 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 →