live_edit_strategy · Refinore MCP: Risk & Policy

WHAT IT DOES

What live_edit_strategy does on Refinore

AI agents use live_edit_strategy to create or update resources in Refinore — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Refinore environment.

WHY IT NEEDS A POLICY

Why live_edit_strategy needs a policy

This tool modifies mining strategy configuration that directly controls autonomous mining operations on the Solana blockchain. While it does not delete strategies (which would be Destructive) or directly execute arbitrary code (which would be Execute), it rewrites strategy logic and parameters that govern ongoing operations.

From the tool's definition Tool description states 'Live-edit a mining strategy' and 'changes take effect on the next deployment round automatically.' The word 'edit' combined with persistence of changes indicates modification of data (mining strategy configuration).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

live_edit_strategy Rate-limited

live_edit_strategy stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "live_edit_strategy": {
      "limits": [
        {
          "counter": "live_edit_strategy_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Refinore, so you can run agents against it safely.

FAQ

Questions about live_edit_strategy

What does the live_edit_strategy tool do? +

Live-edit a mining strategy between rounds WITHOUT stopping the session. Only send the fields you want to change — changes take effect on the next deployment round automatically. Supports updating deterministic custom strategy scripts. It is categorised as a Write tool in the Refinore MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on live_edit_strategy? +

Register the Refinore MCP server in PolicyLayer and add a rule for live_edit_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.

What risk level is live_edit_strategy? +

live_edit_strategy is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit live_edit_strategy? +

Yes. Add a rate_limit block to the live_edit_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.

How do I block live_edit_strategy completely? +

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

What MCP server provides live_edit_strategy? +

live_edit_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.