projects_delete_check
Read projects.delete-check through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/projects-delete-check.md
What projects_delete_check does on Appaloft
AI agents call projects_delete_check to retrieve information from Appaloft without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
projectId | string | Yes |
Parameters from the server's own tool schema.
Why projects_delete_check is rated Low
The tool is explicitly described as 'Read' operation that checks whether a project can be deleted. It retrieves/queries eligibility information without performing any actual deletion. The word 'check' further confirms it is a read/query operation with no side effects.
From the tool's definition 'Read projects.delete-check through the Appaloft application operation catalog'
Attacks that exploit this kind of access
The rule that runs projects_delete_check safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Appaloft, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For projects_delete_check, this is the rule to start with:
projects_delete_check is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Appaloft, apply this rule, and every projects_delete_check call is checked against it from then on.
Questions about projects_delete_check
Read projects.delete-check through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Read tool in the Appaloft MCP Server, which means it retrieves data without modifying state.
projects_delete_check accepts 1 parameter: projectId. Required: projectId. The full parameter table on this page comes from the server's own tool schema.
Register the Appaloft MCP server in PolicyLayer and add a rule for projects_delete_check: 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 Appaloft. Nothing to install.
projects_delete_check is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the projects_delete_check 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 projects_delete_check. 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.
projects_delete_check is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Appaloft, and thousands of servers like it.
This server
Across the catalogue