update_resource_name
AI agents use update_resource_name 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.
The tool performs a Write operation—it updates/modifies a resource name, which is a reversible change. Without explicit description, confidence is moderate but the 'update_' prefix and sibling tools (batch_update_resource_download, batch_update_resource_visibility, configure_paper_basics) that perform similar reversible modifications support Write classification.
From the tool's definition Tool name is 'update_resource_name' which indicates modification of existing data (update). The server context shows this is an educational platform for managing course resources, and 'update' operations modify data reversibly.
Attacks that exploit this kind of access
update_resource_name. 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 update_resource_name: 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.
update_resource_name 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 update_resource_name 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 update_resource_name. 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.
update_resource_name 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 →