delete_goal

THE RISK

Critical Risk

Why delete_goal needs a policy

Deletion of goals is an irreversible operation that cannot be undone. Even though the goal itself is the target (not financial data), deleting a goal destroys all tracking history and associated datapoints.

From the tool's definition Tool name explicitly states "delete" and description confirms "Delete a Beeminder goal." This irreversibly removes a goal and all associated data.

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

POLICY

How to control delete_goal

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

policy.json

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

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

Create a free account and register MCP Beeminder Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP Beeminder Server tools

Destructive delete_datapoint Delete a datapoint. Write create_datapoint create_datapoint Write create_goal create_goal Write create_multiple_datapoints create_multiple_datapoints Write update_goal update_goal Read get_archived_goals Returns all archived goals for the current user that is best presented in a table. Read get_datapoints Returns all datapoints for a specific goal that is best presented in a table. Read get_goal Returns information about a specific goal.

All 11 MCP Beeminder Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in MCP Beeminder Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_goal

What does the delete_goal tool do? +

Delete a Beeminder goal. It is categorised as a Destructive tool in the MCP Beeminder 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 delete_goal? +

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

What risk level is delete_goal? +

delete_goal 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_goal? +

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

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

delete_goal is provided by the MCP Beeminder Server MCP server (strickvl/mcp-beeminder). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Beeminder Server tool call.

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

CHECK YOUR STACK →