AI agents use create_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.
This tool creates a new persistent mining strategy that executes automatically every round on the Solana blockchain. While the creation itself is a Write operation (reversible, since a sibling tool 'delete_strategy' exists), the strategy involves custom scripts that run autonomously and interact with blockchain/financial operations, making misuse potentially high-severity.
From the tool's definition "Create a new auto-mining strategy" and "Supports deterministic custom strategy scripts that run every round"
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Create a new auto-mining strategy with a name and mining parameters. Supports deterministic custom strategy scripts that run every round. 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 create_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.
create_strategy 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 create_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 create_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.
create_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 →