End a goal session. Pass completed=true when the goal was verifiably met (used by the
AI agents call clear_goal to permanently remove resources in Goal Engine — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Clearing/ending a goal session destroys the persistent goal state. Since the server is described as providing 'persistent goal-tracking,' ending/clearing a session removes that persisted data in a way that cannot be undone. This is irreversible deletion of session state, placing it in the Destructive category.
From the tool's definition 'End a goal session' and 'clear_goal' indicate termination/removal of the current goal session, which appears irreversible
Attacks that exploit this kind of access
End a goal session. Pass completed=true when the goal was verifiably met (used by the. It is categorised as a Destructive tool in the Goal Engine MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Goal Engine MCP server in PolicyLayer and add a rule for clear_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 Goal Engine. Nothing to install.
clear_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 clear_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 clear_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.
clear_goal is provided by the Goal Engine MCP server (melihzafer/mcp-goal). 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 →