Delete a saved auto-mining strategy by ID.
AI agents call delete_strategy to permanently remove resources in Refinore — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes a user's saved mining strategy configuration. While not directly moving funds, deletion of strategies that control automated mining operations (as evidenced by sibling tools like 'create_strategy' and 'edit_session') is a destructive action that cannot be undone. An AI agent misusing this could eliminate important user configurations, preventing future mining operations.
From the tool's definition Tool name and function 'Delete a saved auto-mining strategy by ID' indicates irreversible deletion of user data (strategy configuration). The word 'Delete' combined with the action of removing a saved strategy means data cannot be recovered.
Attacks that exploit this kind of access
Delete a saved auto-mining strategy by ID. It is categorised as a Destructive tool in the Refinore MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Refinore MCP server in PolicyLayer and add a rule for delete_strategy: 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 Refinore. Nothing to install.
delete_strategy 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 delete_strategy 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 delete_strategy. 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.
delete_strategy is provided by the Refinore MCP server (jusscubs/refinore-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 →