stop_mining · Refinore MCP: Risk & Policy

WHAT IT DOES

What stop_mining does on Refinore

AI agents invoke stop_mining to trigger actions in Refinore. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why stop_mining needs a policy

stop_mining triggers an external operation on the Solana blockchain that halts an active mining process. This is not a mere data read (Read) nor a reversible modification (Write)—stopping a mining session terminates an ongoing operation with economic consequences (lost mining rewards/session state).

From the tool's definition Tool description: 'Stop an active ORE mining session. Optionally specify a session ID, or stop the current active session.' The tool performs an external blockchain operation (halting an active mining process) whose consequences depend on which session is…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_mining Rate-limited

stop_mining stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "stop_mining": {
      "limits": [
        {
          "counter": "stop_mining_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 stop_mining

What does the stop_mining tool do? +

Stop an active ORE mining session. Optionally specify a session ID, or stop the current active session. It is categorised as a Execute tool in the Refinore MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on stop_mining? +

Register the Refinore MCP server in PolicyLayer and add a rule for stop_mining: 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 stop_mining? +

stop_mining is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit stop_mining? +

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

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

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