AI agents use edit_session 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.
This tool creates or modifies data (mining session parameters) reversibly without deletion. While it operates on blockchain mining (Solana), the edit operation itself is Write-category (updates to session configuration). Severity is high because misconfigured mining sessions could result in unintended token/reward outcomes or financial loss, though the action is reversible by subsequent edits.
From the tool's definition Tool description states 'Live-edit your active mining session' which modifies an ongoing mining session. The phrase 'Only send fields you want to change' indicates selective updates to existing session state.
Attacks that exploit this kind of access
Live-edit your active mining session between rounds WITHOUT stopping/restarting. Only send fields you want to change. For strategy-based sessions, use live_edit_strategy instead. 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.
Register the Refinore MCP server in PolicyLayer and add a rule for edit_session: 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.
edit_session is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the edit_session 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 edit_session. 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.
edit_session 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.
edit_session is one line of Refinore's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →