MCP compliance catalog

Every MCP tool in the SCOPE compliance index, grouped by server — risk posture, regulatory exposure, and the tools that warrant tighter governance.
387MCP servers
5470tools
Reset 387 of 387 servers
Qlik Cloud
25 tools · footprint 66
1 critical 12 high 10 med 2 low COSOSOX
Adobe Workfront
25 tools · footprint 65
2 critical 7 high 13 med 3 low
MailerLite
25 tools · footprint 63
1 critical 11 high 12 med 1 low
MongoDB
25 tools · footprint 63
2 critical 7 high 12 med 4 low
MotherDuck
21 tools · footprint 62
4 critical 5 high 9 med 3 low
QuickNode
22 tools · footprint 61
5 critical 1 high 10 med 6 low COSOPCI+1 more
Salesforce
32 tools · footprint 60
4 critical 2 high 9 med 17 low COSOSOX
Close
64 tools · footprint 59
5 high 22 med 37 low COSOSOX
Cloudflare
26 tools · footprint 58
3 critical 4 high 6 med 13 low
Webflow
23 tools · footprint 57
2 critical 5 high 10 med 6 low
n8n
25 tools · footprint 56
1 critical 7 high 13 med 4 low
Pigment
25 tools · footprint 56
9 high 14 med 2 low COSOSOX
PagerDuty
64 tools · footprint 55
5 high 16 med 43 low
Datadog
24 tools · footprint 52
1 critical 11 high 12 med
Attention
25 tools · footprint 51
1 critical 6 high 18 med
Box
37 tools · footprint 50
10 high 14 med 13 low COSOHIPAA+1 more
‹ PrevPage 2 of 25Next ›
PylonDocs ↗
5 med 6 low · 11 tools · 0 SoD-flagged
regimes APPICCPAGDPRISO_27001LGPDPIPEDAPIPLPOPIASOC2UK_GDPR

Tools needing tighter control (0 of 11)

None — every tool is low-risk, high-confidence, and outside PCI/HIPAA payload scope.
All other tools (11)
pylon.create_issue low conf highallow
Opens a new support ticket that enters the team's queue and SLA clock; reversible, but visible to the customer if the issue is customer-facing.
pylon.get_account low conf highallow
Reads one customer account record with its custom fields, which commonly hold plan tier, renewal dates and internal commercial notes.
pylon.get_contact medium conf highaudit
Retrieves an identified end user's contact record — name, email and account association — pulling customer personal data into the agent context.
pylon.get_issue low conf highallow
Reads one support ticket including its requester, account linkage and custom field values — customer personal data leaves the helpdesk boundary.
pylon.get_issue_messages medium conf highaudit
Returns the complete customer-support conversation thread, which routinely carries contact details, account context and whatever sensitive information the customer pasted into the ticket.
pylon.get_me low conf mediumallow
Identifies which Pylon principal the connection is acting as; confirms the blast radius of the session without touching third-party data.
pylon.get_user low conf mediumallow
Reads an internal team member's profile, exposing employee name and email plus their role in the support org.
pylon.search_accounts low conf highallow
Lists the customer accounts in the workspace along with their domains and tags, exposing the full customer roster to the caller.
pylon.search_issues medium conf highaudit
Enumerates support tickets across every customer account the token can see, surfacing requester identities and issue content in bulk from a single query.
pylon.update_account medium conf highaudit
Overwrites fields on a customer account record; downstream routing, SLA tiers and reporting keyed off those fields shift with no approval step.
pylon.update_issue medium conf highaudit
Changes ticket status, ownership or custom fields, which moves SLA state and reassigns work — an agent closing tickets silently skews support reporting.