AI agents invoke run_funnel_simulation to trigger actions in Wyckoff Trading Agent 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 'run_' prefix indicates the tool executes a simulation rather than passively reading or writing data. Simulations are Execute-category tools because they trigger computational operations whose outcomes depend on input parameters. The empty description reduces confidence, but the naming pattern and server context (trading analysis with backtesting) support Execute classification.
From the tool's definition Tool named 'run_funnel_simulation' with empty description. Context indicates this is a Wyckoff trading analysis server with backtesting and simulation capabilities. The 'run_' prefix strongly suggests code execution or computational simulation.
Documented attack patterns abuse exactly the kind of access run_funnel_simulation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Wyckoff Trading Agent MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for run_funnel_simulation:
{
"version": "1",
"default": "deny",
"tools": {
"run_funnel_simulation": {
"limits": [
{
"counter": "run_funnel_simulation_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_funnel_simulation 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.
run_funnel_simulation. It is categorised as a Execute tool in the Wyckoff Trading Agent MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Wyckoff Trading Agent MCP Server MCP server in PolicyLayer and add a rule for run_funnel_simulation: 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 Wyckoff Trading Agent MCP Server. Nothing to install.
run_funnel_simulation 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_funnel_simulation 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 run_funnel_simulation. 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_funnel_simulation is provided by the Wyckoff Trading Agent MCP Server MCP server (youngcan-wang/wyckofftradingagent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 15 Wyckoff Trading Agent MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
15 Wyckoff Trading Agent MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.