delete_person

Soft-delete a person.

SERVERStarfield SOURCE@adrata/starfield-mcp

Critical RISK CLASS

Category Destructive

Parameters 11 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adrata-starfield-mcp/delete-person.md

WHAT IT DOES

What delete_person does on Starfield

AI agents call delete_person to permanently remove resources in Starfield, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Parameter	Type	Required	Description
`id`	string	Yes

Parameters from the server's own tool schema.

RISK

Why delete_person is rated Critical

An AI agent that decides to call delete_person doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Starfield is gone. There is no undo for destructive operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_person safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Starfield, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_person, this is the rule to start with:

delete_person Hidden

delete_person is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_person"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about delete_person

What does the delete_person tool do? +

Soft-delete a person. It is categorised as a Destructive tool in the Starfield MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does delete_person accept? +

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

How do I enforce a policy on delete_person? +

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

What risk level is delete_person? +

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

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

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

delete_person is provided by the Starfield MCP server (@adrata/starfield-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Starfield, and thousands of servers like it.

This server

All 233 Starfield tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →