Medium Risk

telora_product_issue

Task tracking: manage issues (tasks, bugs, context groups) within deliveries. Issues flow through To Do -> In Progress -> Done. Context groups organize related tasks with shared files and AI context. Actions: list issues (by delivery or product-wide), create an issue (title + deliveryId), update ...

High parameter count (17 properties)

Part of the Mcp Products MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@telora/mcp-products Write Risk 2/5

AI agents use telora_product_issue to create or modify resources in Mcp Products. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call telora_product_issue repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Mcp Products.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

mcp-products.yaml
tools:
  telora_product_issue:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Mcp Products policy for all 11 tools.

Tool Name telora_product_issue
Category Write
Risk Level Medium

View all 11 tools →

Agents calling write-class tools like telora_product_issue have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the telora_product_issue tool do? +

Task tracking: manage issues (tasks, bugs, context groups) within deliveries. Issues flow through To Do -> In Progress -> Done. Context groups organize related tasks with shared files and AI context. Actions: list issues (by delivery or product-wide), create an issue (title + deliveryId), update issue fields (status, priority, description), delete an issue.. It is categorised as a Write tool in the Mcp Products MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on telora_product_issue? +

Add a rule in your Intercept YAML policy under the tools section for telora_product_issue. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mcp Products MCP server.

What risk level is telora_product_issue? +

telora_product_issue is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit telora_product_issue? +

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

How do I block telora_product_issue completely? +

Set action: deny in the Intercept policy for telora_product_issue. 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 telora_product_issue? +

telora_product_issue 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.

Enforce policies on Mcp Products

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.