deletecontext
AI agents call deletecontext to permanently remove resources in Student MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The 'delete' prefix in the tool name indicates a destructive operation. Given the server manages student knowledge graphs with sessions and contexts (as evidenced by sibling tools: startsession, endsession, loadcontext, buildcontext), 'deletecontext' most likely permanently removes a stored context/knowledge graph, which would be irreversible.
From the tool's definition Tool name 'deletecontext' strongly implies irreversible deletion of a context (student knowledge graph session data). Description is empty, lowering confidence.
Attacks that exploit this kind of access
deletecontext. It is categorised as a Destructive tool in the Student MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Student MCP Server MCP server in PolicyLayer and add a rule for deletecontext: 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 Student MCP Server. Nothing to install.
deletecontext 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 deletecontext 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 deletecontext. 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.
deletecontext is provided by the Student MCP Server MCP server (tejpalvirk/student). 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 →