Manage projects. Actions: - list (default): List all projects in the current team. - update: Update a project's name or description. Uses the connected project unless 'slug' is provided. - delete: Delete a project and all its data. Uses the connected project unless 'slug' is provided.
Part of the Cantrip server.
Free to start. No card required.
AI agents may call cantrip_project to permanently remove or destroy resources in Cantrip. 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 cantrip_project in a loop, permanently destroying resources in Cantrip. 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.
{
"version": "1",
"default": "deny",
"hide": [
"cantrip_project"
]
}See the full Cantrip policy for all 19 tools.
These attack patterns abuse exactly the kind of access cantrip_project gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Manage projects. Actions: - list (default): List all projects in the current team. - update: Update a project's name or description. Uses the connected project unless 'slug' is provided. - delete: Delete a project and all its data. Uses the connected project unless 'slug' is provided.. It is categorised as a Destructive tool in the Cantrip MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Cantrip MCP server in PolicyLayer and add a rule for cantrip_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 Cantrip. Nothing to install.
cantrip_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 cantrip_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 cantrip_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.
cantrip_project is provided by the Cantrip MCP server (mcp-server-cantrip). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 19 Cantrip 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.