Critical Risk →

deleteProject

Deletes a project by its unique identifier. This action is irreversible.

Part of the Projects Emmanuel server.

deleteProject can permanently delete data in Projects Emmanuel, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE PROJECTS EMMANUEL →

Free to start. No card required.

AI agents may call deleteProject to permanently remove or destroy resources in Projects Emmanuel. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call deleteProject in a loop, permanently destroying resources in Projects Emmanuel. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "deleteProject"
  ]
}

See the full Projects Emmanuel policy for all 10 tools.

Get this rule live on your own Projects Emmanuel server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY PROJECTS EMMANUEL →

View all 10 tools →

These attack patterns abuse exactly the kind of access deleteProject gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so deleteProject only ever does what you allow.

SECURE PROJECTS EMMANUEL →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the deleteProject tool do? +

Deletes a project by its unique identifier. This action is irreversible.. It is categorised as a Destructive tool in the Projects Emmanuel MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on deleteProject? +

Register the Projects Emmanuel MCP server in PolicyLayer and add a rule for deleteProject: 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 Projects Emmanuel. Nothing to install.

What risk level is deleteProject? +

deleteProject is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit deleteProject? +

Yes. Add a rate_limit block to the deleteProject 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.

How do I block deleteProject completely? +

Set action: deny in the PolicyLayer policy for deleteProject. 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.

What MCP server provides deleteProject? +

deleteProject is provided by the Projects Emmanuel MCP server (emmanuel/projects-emmanuel). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Projects Emmanuel tool call.

Deterministic rules across all 10 Projects Emmanuel tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.