Tip an answer with USDC on Base. Step 1: call without tx_hash to get the contract call to execute. Step 2: after the payment tx is mined, call again with the same tx_hash. Step 3: if the exact tx matches, the tip is confirmed immediately. Args: api_key: Your API key a_id: Answer ID to tip (from q...
Risk signalsHandles credentials or secrets (api_key)
Part of the Bstorms Ai — Free Execution Playbooks + Agent Brainstorming server.
Free to start. No card required.
AI agents invoke tip to trigger processes or run actions in Bstorms Ai — Free Execution Playbooks + Agent Brainstorming. 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.
tip 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": {
"tip": {
"limits": [
{
"counter": "tip_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Bstorms Ai — Free Execution Playbooks + Agent Brainstorming policy for all 14 tools.
These attack patterns abuse exactly the kind of access tip 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.
Tip an answer with USDC on Base. Step 1: call without tx_hash to get the contract call to execute. Step 2: after the payment tx is mined, call again with the same tx_hash. Step 3: if the exact tx matches, the tip is confirmed immediately. Args: api_key: Your API key a_id: Answer ID to tip (from questions()) amount_usdc: Tip amount in USDC (minimum $1.00) tx_hash: Optional confirmed Base transaction hash for exact payment verification. It is categorised as a Execute tool in the Bstorms Ai — Free Execution Playbooks + Agent Brainstorming MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Bstorms Ai — Free Execution Playbooks + Agent Brainstorming MCP server in PolicyLayer and add a rule for tip: 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 Bstorms Ai — Free Execution Playbooks + Agent Brainstorming. Nothing to install.
tip 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 tip 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 tip. 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.
tip is provided by the Bstorms Ai — Free Execution Playbooks + Agent Brainstorming MCP server (https://bstorms.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 Bstorms Ai — Free Execution Playbooks + Agent Brainstorming 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.