AI agents call tool_delete_rubric_item to permanently remove resources in Gradescope MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of rubric items is irreversible and directly impacts grading frameworks that instructors and TAs rely on. Removing rubric criteria can break existing grading workflows, affect consistency of graded submissions, and require manual remediation. The action cannot be undone programmatically.
From the tool's definition Tool name is 'tool_delete_rubric_item' with empty description. The verb 'delete' paired with 'rubric_item' in an educational grading context (Gradescope) indicates permanent removal of rubric criteria used in grading workflows.
Documented attack patterns abuse exactly the kind of access tool_delete_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_delete_rubric_item:
{
"version": "1",
"default": "deny",
"hide": [
"tool_delete_rubric_item"
]
} tool_delete_rubric_item disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
tool_delete_rubric_item. It is categorised as a Destructive tool in the Gradescope MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Gradescope MCP Server MCP server in PolicyLayer and add a rule for tool_delete_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_delete_rubric_item is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the tool_delete_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_delete_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_delete_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.