Critical Risk →

invites_delete

invites_delete

How to control invites_delete ↓

What invites_delete does on Ghost MCP Server

AI agents call invites_delete to permanently remove resources in Ghost MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why invites_delete needs a policy

Deletion operations are irreversible and permanently remove data. The tool lacks descriptive documentation, making detailed impact assessment difficult, but the function name and server context (Ghost CMS user management via JWT authentication) indicate this removes invitation records that cannot be restored. Combined with sibling tools like members_delete, this follows a destructive pattern.

From the tool's definition Tool name 'invites_delete' with no description provided. In CMS contexts, invitation deletion is irreversible removal of access credentials/invitations.

Documented attack patterns abuse exactly the kind of access invites_delete gives an agent:

How to control invites_delete

PolicyLayer is an MCP gateway — it sits between your AI agents and Ghost MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for invites_delete:

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

invites_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Ghost MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about invites_delete

What does the invites_delete tool do? +

invites_delete. It is categorised as a Destructive tool in the Ghost MCP Server 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 invites_delete? +

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

What risk level is invites_delete? +

invites_delete 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 invites_delete? +

Yes. Add a rate_limit block to the invites_delete 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 invites_delete completely? +

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

invites_delete is provided by the Ghost MCP Server MCP server (mfydev/ghost-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ghost MCP Server tool call.

Start from Ghost MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

42 Ghost MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.