AI agents use tool_update_rubric_item to create or update resources in Gradescope MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gradescope MCP Server environment.
This tool modifies rubric items used in grading workflows. While reversible (Write rather than Destructive), misuse could corrupt grading rubrics affecting all future assignments in a course, impacting academic integrity and student evaluations. Severity is high because rubrics are critical to fair grading.
From the tool's definition Tool name 'tool_update_rubric_item' indicates modification of rubric data. Sibling tools include 'tool_create_rubric_item' and 'tool_delete_rubric_item', establishing this server's domain as rubric manipulation.
Documented attack patterns abuse exactly the kind of access tool_update_rubric_item gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Gradescope MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for tool_update_rubric_item:
{
"version": "1",
"default": "deny",
"tools": {
"tool_update_rubric_item": {
"limits": [
{
"counter": "tool_update_rubric_item_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} tool_update_rubric_item stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
tool_update_rubric_item. It is categorised as a Write tool in the Gradescope MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gradescope MCP Server MCP server in PolicyLayer and add a rule for tool_update_rubric_item: 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 Gradescope MCP Server. Nothing to install.
tool_update_rubric_item 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 tool_update_rubric_item 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 tool_update_rubric_item. 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.
tool_update_rubric_item is provided by the Gradescope MCP Server MCP server (yuanpeng-li/gradescope-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Gradescope MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
37 Gradescope MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.