// SCAN REPORT

Pylon

38 tools. 15 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 5 Jul 2026

15 can modify or destroy data

23 read-only

38 tools total

Community server · catalogue entry verified 05/07/2026

How to control Pylon ↓

TOOL MAP

What Pylon exposes to your agents

Read (23) Write / Execute (14) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Pylon tools

Destructive · High pylon_delete_issue This tool irreversibly deletes data (an issue record) and explicitly cannot be undone. Write · Medium pylon_remove_issue_followers Removing followers from an issue modifies the issue's follower list, but this is a reversible action (followers can be re-added). Write · Low pylon_remove_tags Removing tags is a reversible modification — tags can be re-added using pylon_add_tags. Write · Medium pylon_add_issue_followers Adding followers to an issue is a write operation that creates relationships or modifies issue state.

15 of Pylon's 38 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Pylon

PolicyLayer is an MCP gateway — it sits between your AI agents and Pylon, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "pylon_delete_issue": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "pylon_add_issue_followers": {
    "limits": [
      {
        "counter": "pylon_add_issue_followers_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "pylon_find_similar_issues_for_account": {
    "limits": [
      {
        "counter": "pylon_find_similar_issues_for_account_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Pylon — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON PYLON →

Instant setup, no code required.

FULL CATALOGUE

All 38 Pylon tools

DESTRUCTIVE 1 tools

Destructive pylon_delete_issue ⚠️ Permanently delete a Pylon issue. This cannot be undone. Verify the correct issue ID before proceeding.

WRITE 14 tools

Write pylon_add_issue_followers Add team members (user_ids) or customers (contact_ids) as followers to a Pylon issue. Write pylon_add_tags Add tags to a Pylon issue without removing existing tags. To replace all tags, use pylon_update_issue; to remo Write pylon_create_attachment_from_url Create a Pylon attachment by downloading a file from a public URL. Write pylon_create_contact Create a new customer contact in Pylon. Use carefully. Write pylon_create_issue Create a new support issue/ticket in Pylon. Write pylon_create_knowledge_base_article Create a new help article in a knowledge base. Write pylon_create_tag Create a new tag for categorizing issues and contacts. Write pylon_create_team Create a new support team in Pylon. Write pylon_link_external_issue Link a Linear, Jira, GitHub, or Asana issue to a Pylon support issue for cross-system tracking. Write pylon_remove_issue_followers Remove team members or customers from following a Pylon issue. Write pylon_remove_tags Remove specific tags from a Pylon issue without affecting other tags. To add tags, use pylon_add_tags; to repl Write pylon_snooze_issue Temporarily hide an issue until a future date/time for deferred follow-up. Write pylon_unlink_external_issue Remove the link between a Pylon issue and an external ticketing system issue. Write pylon_update_issue Update an existing issue

READ 23 tools

Read pylon_find_similar_issues_for_account Find issues from the same company/account to identify company-wide problems. Read pylon_find_similar_issues_for_requestor Find issues from the same requestor as the source issue to identify recurring patterns. Read pylon_find_similar_issues_global Find similar issues across all accounts to identify widespread issues or find past solutions. Read pylon_get_account Get details of a specific customer account. Read pylon_get_accounts Get all customer accounts from Pylon. Read pylon_get_attachment Get attachment metadata by ID. Use when you have an attachment_id from an issue message. Download the file usi Read pylon_get_contacts Get customer contacts from Pylon. Returns contact details like name, email, and company. Read pylon_get_issue Get complete details of a specific issue. Prefer this over message tools when you only need issue metadata. Read pylon_get_issue_followers Get all users and contacts following a Pylon issue. Read pylon_get_issue_messages Get the message history for an issue. Use when you need message content, not just issue metadata. Read pylon_get_issue_with_messages Get an issue with its full conversation history. Prefer pylon_get_issue when you only need issue details. Read pylon_get_issues Get support issues within a time range (max 30 days); defaults to last 30 days. Use this for unfiltered listin Read pylon_get_knowledge_bases Get all knowledge bases in Pylon. Read pylon_get_me Get the current authenticated user profile including name, email, role, and permissions. Read pylon_get_tags Get all available tags for categorizing issues and contacts. Read pylon_get_team Get details of a specific support team including members and workload. Read pylon_get_teams Get all support teams in Pylon. Read pylon_get_ticket_forms Get all ticket submission forms available to customers. Read pylon_get_users Get all team members and support agents in your Pylon workspace. Read pylon_search_contacts Search for customer contacts by name, email, company, or phone. Read pylon_search_issues Search issues using structured filters; requires at least one filter. For unfiltered listing, use pylon_get_is Read pylon_search_issues_by_status Search issues by status name, including custom statuses like Read pylon_search_users Search for team members and support agents by name, email, or department.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Pylon

Can an AI agent delete data through the Pylon MCP server? +

Yes. The Pylon server exposes 1 destructive tools including pylon_delete_issue. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Pylon? +

The Pylon server has 14 write tools including pylon_add_issue_followers, pylon_add_tags, pylon_create_attachment_from_url. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Pylon.

How many tools does the Pylon MCP server expose? +

38 tools across 3 categories: Destructive, Read, Write. 23 are read-only. 15 can modify, create, or delete data.

How do I enforce a policy on Pylon? +

Register the Pylon MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Pylon tool call.

Deterministic rules across all 38 Pylon tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON PYLON →

Instant setup, no code required.

38 Pylon tools catalogued and risk-classified — across an index of 43,000+ MCP servers.