AI agents invoke utility_formula_run to trigger actions in TdxQuant 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.
Although the description is empty (lowering confidence slightly), the name 'run' paired with 'formula' in a financial trading MCP server strongly suggests code execution. Formula execution in financial contexts can trigger trades, modify positions, or produce outputs that influence irreversible financial actions. This exceeds Write (reversible modifications) and qualifies as Execute.
From the tool's definition Tool name 'utility_formula_run' indicates execution of formulas/code; combined with server context providing trading capabilities and financial operations, this tool likely executes arbitrary financial formulas or calculations that could affect trading…
Documented attack patterns abuse exactly the kind of access utility_formula_run gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TdxQuant MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for utility_formula_run:
{
"version": "1",
"default": "deny",
"tools": {
"utility_formula_run": {
"limits": [
{
"counter": "utility_formula_run_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}utility_formula_run 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.
utility_formula_run. It is categorised as a Execute tool in the TdxQuant MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the TdxQuant MCP Server MCP server in PolicyLayer and add a rule for utility_formula_run: 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 TdxQuant MCP Server. Nothing to install.
utility_formula_run 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 utility_formula_run 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 utility_formula_run. 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.
utility_formula_run is provided by the TdxQuant MCP Server MCP server (lingfan/tdxquant-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from TdxQuant 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.
39 TdxQuant MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.