Execution roadmap: group deliveries into themed work scopes. Strategies define what the AI daemon works on -- assigning an agent role queues the strategy for autonomous execution. Actions: list strategies for a product, create a strategy (name + productId), update strategy settings (description, ...
High parameter count (24 properties); Single-target operation
Part of the Mcp Products MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke telora_product_strategy to trigger processes or run actions in Mcp Products. 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.
telora_product_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:
telora_product_strategy:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Mcp Products policy for all 11 tools.
Agents calling execute-class tools like telora_product_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.
telora_product_strategy is one of the high-risk operations in Mcp Products. 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.
Execution roadmap: group deliveries into themed work scopes. Strategies define what the AI daemon works on -- assigning an agent role queues the strategy for autonomous execution. Actions: list strategies for a product, create a strategy (name + productId), update strategy settings (description, status, agent role, pipeline config), reorder strategy priority, merges (list merge history for a strategy), retrospective_trigger (create a pending retrospective for a strategy), retrospective_run (execute a pending retrospective via LLM), retrospective_list (list retrospectives for a strategy), retrospective_get (get a single retrospective by ID).. It is categorised as a Execute tool in the Mcp Products 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 telora_product_strategy. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mcp Products MCP server.
telora_product_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 telora_product_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 telora_product_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.
telora_product_strategy is provided by the Mcp Products MCP server (@telora/mcp-products). 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