Execute a Python strategy code asynchronously. The code can: - Read live prices from LTP_STORE using: key = f"{scrip_code}_{exchange}" - Place orders using the async function func_place_order: - subscribe(scrip_code, exchange) → async function to subscribe to a symbol - unsubscribe(scrip_co...
Bulk/mass operation — affects multiple targets
Part of the Blinkxmcp MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke run_strategy to trigger processes or run actions in Blinkxmcp. 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.
run_strategy can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept 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.
tools:
run_strategy:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Blinkxmcp policy for all 12 tools.
Agents calling execute-class tools like run_strategy have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
run_strategy is one of the high-risk operations in Blinkxmcp. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Execute a Python strategy code asynchronously. The code can: - Read live prices from LTP_STORE using: key = f"{scrip_code}_{exchange}" - Place orders using the async function func_place_order: - subscribe(scrip_code, exchange) → async function to subscribe to a symbol - unsubscribe(scrip_code, exchange) → async function to unsubscribe from a symbol - get_token(session_id: str) -> to get token for order placement, session id always to be sent by ai agent, possible output {"status": "ok", "access_token": access_token} or return {"status": "error", "access_token": None, "message": "Session ID not found in tokens file"} Arguments for func_place_order: - api_url: string, API endpoint (default: BlinkX regular order URL) - token: string, authentication token - tradingsymbol: string, symbol of the instrument (required) - exchange: string, exchange (e.g., NSE, BSE) - transaction_type: BUY or SELL - order_type: LIMIT or MARKET - quantity: int, number of shares/contracts - product: string, product type - validity: string, DAY or IOC - price: float, price for LIMIT orders Example strategy code: key = f'-1_NSE' ltp = LTP_STORE.get(key, 0) if ltp > 26100: await func_place_order(tradingsymbol='-1', exchange='NSE', transaction_type='BUY', price=ltp, quantity=1) always unsubscribe to symbol after placing order and always ensure proper logging for every iteration to get status of execution in format session ID: "Required logs" and use default logging ie already existing 'logger'. It is categorised as a Execute tool in the Blinkxmcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for run_strategy. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Blinkxmcp MCP server.
run_strategy 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 run_strategy rule in your Intercept 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 Intercept policy for run_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.
run_strategy is provided by the Blinkxmcp MCP server (ai/blinkxmcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept