New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

tengu_v3_backtest_run_detail

Detail for a single backtest run

SERVERTengu SOURCEHlobo-dev/tengu-mcp
High RISK CLASS
Category Execute
Parameters 11 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/tengu-mcp/tengu-v3-backtest-run-detail.md

What tengu_v3_backtest_run_detail does on Tengu

AI agents invoke tengu_v3_backtest_run_detail to trigger actions in Tengu. 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.

ParameterTypeRequiredDescription
run_id string Yes Path parameter 'run_id' (required).

Parameters from the server's own tool schema.

Why tengu_v3_backtest_run_detail is rated High

tengu_v3_backtest_run_detail triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Questions about tengu_v3_backtest_run_detail

What does the tengu_v3_backtest_run_detail tool do? +

Detail for a single backtest run. It is categorised as a Execute tool in the Tengu MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does tengu_v3_backtest_run_detail accept? +

tengu_v3_backtest_run_detail accepts 1 parameter: run_id. Required: run_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on tengu_v3_backtest_run_detail? +

Register the Tengu MCP server in PolicyLayer and add a rule for tengu_v3_backtest_run_detail: 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 Tengu. Nothing to install.

What risk level is tengu_v3_backtest_run_detail? +

tengu_v3_backtest_run_detail is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit tengu_v3_backtest_run_detail? +

Yes. Add a rate_limit block to the tengu_v3_backtest_run_detail 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.

How do I block tengu_v3_backtest_run_detail completely? +

Set action: deny in the PolicyLayer policy for tengu_v3_backtest_run_detail. 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.

What MCP server provides tengu_v3_backtest_run_detail? +

tengu_v3_backtest_run_detail is provided by the Tengu MCP server (Hlobo-dev/tengu-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Tengu, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Tengu's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.