pylon_link_external_issue · Pylon MCP: Risk & Policy

WHAT IT DOES

What pylon_link_external_issue does on Pylon

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

WHY IT NEEDS A POLICY

Why pylon_link_external_issue needs a policy

This tool creates a bidirectional or persistent reference between a Pylon issue and an external issue in another system. While it does not directly modify the content of either issue, it establishes a new data relationship that can affect workflows and tracking. This is a reversible write operation (the link can typically be removed), distinguishing it from destructive actions.

From the tool's definition Link a Linear, Jira, GitHub, or Asana issue to a Pylon support issue for cross-system tracking — 'link' indicates creating an association or reference between two external entities.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pylon_link_external_issue Rate-limited

pylon_link_external_issue 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": {
    "pylon_link_external_issue": {
      "limits": [
        {
          "counter": "pylon_link_external_issue_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 Pylon, so you can run agents against it safely.

FAQ

Questions about pylon_link_external_issue

What does the pylon_link_external_issue tool do? +

Link a Linear, Jira, GitHub, or Asana issue to a Pylon support issue for cross-system tracking. It is categorised as a Write tool in the Pylon MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on pylon_link_external_issue? +

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

What risk level is pylon_link_external_issue? +

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

Can I rate-limit pylon_link_external_issue? +

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

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

pylon_link_external_issue is provided by the Pylon MCP server (@customer-support-success/pylon-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.