AI agents call deletecontext to permanently remove resources in Project MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The name begins with 'delete', which typically indicates an irreversible removal operation. In the context of a project knowledge graph server, deleting a context could remove structured project data (tasks, milestones, resources, team members) that cannot be recovered. The description is empty, which lowers confidence, but the naming convention and server context strongly suggest a Destructive operation.
From the tool's definition Tool name 'deletecontext' strongly implies irreversible deletion of a context object within the project knowledge graph.
Documented attack patterns abuse exactly the kind of access deletecontext gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Project MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for deletecontext:
{
"version": "1",
"default": "deny",
"hide": [
"deletecontext"
]
}deletecontext 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.
deletecontext. It is categorised as a Destructive tool in the Project MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Project 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 Project 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 Project MCP Server MCP server (tejpalvirk/project). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Project 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.
6 Project MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.