AI agents invoke strategy_buy_with_stop_loss to trigger actions in FinQ4Cn MCP Server. 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.
The tool name implies executing a buy trading strategy with stop-loss parameters, which could trigger real financial transactions. However, given the server is described as providing data for quantitative analysis and backtesting, this may be a backtesting/simulation tool rather than live trading. The empty description significantly lowers confidence.
From the tool's definition Tool name 'strategy_buy_with_stop_loss' suggests executing a trading strategy with buy orders and stop-loss logic; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access strategy_buy_with_stop_loss gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and FinQ4Cn MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for strategy_buy_with_stop_loss:
{
"version": "1",
"default": "deny",
"tools": {
"strategy_buy_with_stop_loss": {
"limits": [
{
"counter": "strategy_buy_with_stop_loss_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}strategy_buy_with_stop_loss 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.
strategy_buy_with_stop_loss. It is categorised as a Execute tool in the FinQ4Cn MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the FinQ4Cn MCP Server MCP server in PolicyLayer and add a rule for strategy_buy_with_stop_loss: 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 FinQ4Cn MCP Server. Nothing to install.
strategy_buy_with_stop_loss 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 strategy_buy_with_stop_loss 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 strategy_buy_with_stop_loss. 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.
strategy_buy_with_stop_loss is provided by the FinQ4Cn MCP Server MCP server (jinhongzou/finq4cn-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from FinQ4Cn MCP Server, 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.
13 FinQ4Cn MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.