Registry se project hataao (path delete nahi hoga, sirf naam mapping remove hogi)
AI agents call deregister_project to permanently remove resources in Universal Dev MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Although the tool explicitly states the path/files are not deleted ('path delete nahi hoga'), it irreversibly removes the name-to-path mapping from the registry. This is a destructive, non-reversible removal of configuration data (the registry entry), which fits the Destructive category. Severity is medium because only the registry mapping is lost, not actual project files.
From the tool's definition 'Registry se project hataao' (remove project from registry) and 'sirf naam mapping remove hogi' (only name mapping will be removed) — permanently removes the project registration/mapping
Attacks that exploit this kind of access
Registry se project hataao (path delete nahi hoga, sirf naam mapping remove hogi). It is categorised as a Destructive tool in the Universal Dev MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Universal Dev MCP server in PolicyLayer and add a rule for deregister_project: 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 Universal Dev MCP. Nothing to install.
deregister_project 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 deregister_project 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 deregister_project. 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.
deregister_project is provided by the Universal Dev MCP server (kallusuvaidyam/universal_mcp). 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 →