Permanently delete a goal. This action cannot be undone.
AI agents call rybbit_delete_goal to permanently remove resources in Rybbit — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data (a goal configuration) with no recovery option. While the blast radius is limited to goal configurations rather than critical business data, the permanent nature and inability to undo the action classify it as Destructive rather than Write. High severity reflects the irreversibility, though impact depends on how critical the goal is to the business.
From the tool's definition Tool description states 'Permanently delete a goal. This action cannot be undone.' The words 'Permanently delete' and 'cannot be undone' are explicit indicators of irreversible data destruction.
Attacks that exploit this kind of access
Permanently delete a goal. This action cannot be undone. It is categorised as a Destructive tool in the Rybbit MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Rybbit MCP server in PolicyLayer and add a rule for rybbit_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 Rybbit. Nothing to install.
rybbit_delete_goal is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the rybbit_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.
Set action: deny in the PolicyLayer policy for rybbit_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.
rybbit_delete_goal is provided by the Rybbit MCP server (nks-hub/rybbit-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →