link_feedback_to_jira · ProduckAI MCP Server MCP

WHAT IT DOES

What link_feedback_to_jira does on ProduckAI MCP Server

AI agents use link_feedback_to_jira to create or update resources in ProduckAI MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ProduckAI MCP Server environment.

WHY IT NEEDS A POLICY

Why link_feedback_to_jira needs a policy

This tool creates an association/relationship between two existing records (feedback item and JIRA issue). It is a reversible write operation — creating a link — with no code execution, deletion, or financial impact. Misuse could corrupt product management data by creating incorrect linkages, but the blast radius is moderate since links can typically be removed.

From the tool's definition 'Manually link a feedback item to an existing JIRA issue' and 'connect feedback to issues created outside the sync process'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

link_feedback_to_jira Rate-limited

link_feedback_to_jira stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "link_feedback_to_jira": {
      "limits": [
        {
          "counter": "link_feedback_to_jira_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ProduckAI MCP Server, so you can run agents against it safely.

FAQ

Questions about link_feedback_to_jira

What does the link_feedback_to_jira tool do? +

Manually link a feedback item to an existing JIRA issue. Use this to connect feedback to issues created outside the sync process. It is categorised as a Write tool in the ProduckAI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on link_feedback_to_jira? +

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

What risk level is link_feedback_to_jira? +

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

Can I rate-limit link_feedback_to_jira? +

Yes. Add a rate_limit block to the link_feedback_to_jira 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 link_feedback_to_jira completely? +

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

link_feedback_to_jira is provided by the ProduckAI MCP Server MCP server (rohitsaraff33-bit/produckai-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.