AI agents invoke stop_campaign to trigger actions in Boosty MCP DeFi Platform. 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.
Stopping and finalizing a campaign triggers an external operation that halts ongoing DeFi activity (trading, volume generation) and commits a final state. This is an Execute-level action because it triggers external operations on blockchain infrastructure. While it stops activity rather than deleting data, finalization may have irreversible side effects (e.g., settling positions, closing orders).
From the tool's definition 'Stop and finalize a campaign' — terminates an active DeFi campaign (e.g., volume generation or trading campaign) and finalizes it
Documented attack patterns abuse exactly the kind of access stop_campaign gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Boosty MCP DeFi Platform, and nothing reaches the server without passing your rules. This is the rule we recommend for stop_campaign:
{
"version": "1",
"default": "deny",
"tools": {
"stop_campaign": {
"limits": [
{
"counter": "stop_campaign_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}stop_campaign 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.
Free to start. No card required.
Stop and finalize a campaign. It is categorised as a Execute tool in the Boosty MCP DeFi Platform MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Boosty MCP DeFi Platform MCP server in PolicyLayer and add a rule for stop_campaign: 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 Boosty MCP DeFi Platform. Nothing to install.
stop_campaign 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 stop_campaign 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 stop_campaign. 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.
stop_campaign is provided by the Boosty MCP DeFi Platform MCP server (nirholas/boosty). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Boosty MCP DeFi Platform, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
80 Boosty MCP DeFi Platform tools catalogued and risk-classified — across an index of 43,000+ MCP servers.