Execute a Day 1 Toreva strategy on Solana. Public scope is exactly three products: Earn, Stake, and Balance. Runtime strategy ids are normalized behind public product ids and hidden strategy toggles are rejected. Non-custodial. Every action receipted.
Risk signalsHigh parameter count (10 properties) · Bulk/mass operation — affects multiple targets
Part of the Kit server.
Free to start. No card required.
AI agents invoke toreva_execute to trigger processes or run actions in Kit. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
toreva_execute can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"toreva_execute": {
"limits": [
{
"counter": "toreva_execute_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Kit policy for all 23 tools.
These attack patterns abuse exactly the kind of access toreva_execute gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Execute a Day 1 Toreva strategy on Solana. Public scope is exactly three products: Earn, Stake, and Balance. Runtime strategy ids are normalized behind public product ids and hidden strategy toggles are rejected. Non-custodial. Every action receipted.. It is categorised as a Execute tool in the Kit MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kit MCP server in PolicyLayer and add a rule for toreva_execute: 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 Kit. Nothing to install.
toreva_execute is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the toreva_execute 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 toreva_execute. 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.
toreva_execute is provided by the Kit MCP server (@toreva/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 23 Kit tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.