servers_delete_check

Read servers.delete-check through the Appaloft application operation catalog. Shared with CLI and HTTP/API.

SERVERAppaloft SOURCE@appaloft/mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/appaloft-mcp/servers-delete-check.md

WHAT IT DOES

What servers_delete_check does on Appaloft

AI agents call servers_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
`serverId`	string	Yes

Parameters from the server's own tool schema.

RISK

Why servers_delete_check is rated Low

The description explicitly states this tool 'reads' the delete-check operation — it queries/retrieves information about whether a server can be deleted, rather than performing the deletion itself. The actual deletion would be a separate destructive action.

From the tool's definition 'Read servers.delete-check through the Appaloft application operation catalog'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs servers_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 servers_delete_check, this is the rule to start with:

servers_delete_check Allowed

servers_delete_check is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "servers_delete_check": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Appaloft, apply this rule, and every servers_delete_check call is checked against it from then on.

FAQ

Questions about servers_delete_check

What does the servers_delete_check tool do? +

Read servers.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.

What parameters does servers_delete_check accept? +

servers_delete_check accepts 1 parameter: serverId. Required: serverId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on servers_delete_check? +

Register the Appaloft MCP server in PolicyLayer and add a rule for servers_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.

What risk level is servers_delete_check? +

servers_delete_check is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit servers_delete_check? +

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

How do I block servers_delete_check completely? +

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

What MCP server provides servers_delete_check? +

servers_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.

KEEP EXPLORING

More on Appaloft, and thousands of servers like it.

This server

All 358 Appaloft tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →