AI agents call get_campaign_status to retrieve information from Boosty MCP DeFi Platform without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about an existing campaign's status. It performs no modifications, deletions, or financial transactions. While the server as a whole manages DeFi operations with financial implications, this specific tool is a simple data query operation.
From the tool's definition Tool name 'get_campaign_status' and description 'Get current status of a campaign' indicate a retrieval operation with no side effects. The verb 'Get' and the query nature of status retrieval are characteristic of Read operations.
Documented attack patterns abuse exactly the kind of access get_campaign_status 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 get_campaign_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_campaign_status": {}
}
}get_campaign_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get current status of a campaign. It is categorised as a Read tool in the Boosty MCP DeFi Platform MCP Server, which means it retrieves data without modifying state.
Register the Boosty MCP DeFi Platform MCP server in PolicyLayer and add a rule for get_campaign_status: 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.
get_campaign_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_campaign_status 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 get_campaign_status. 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.
get_campaign_status 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.