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
Everlaw
8 tools · footprint 12
1 high 7 low
Fyxer
6 tools · footprint 12
3 med 3 low
Krisp
6 tools · footprint 12
2 med 4 low
LatchBio
9 tools · footprint 12
2 med 7 low
Linear
21 tools · footprint 12
3 med 18 low
Microsoft Power BI
4 tools · footprint 12
1 high 3 low
Plaid
5 tools · footprint 12
1 med 4 low GLBA
Pylon
11 tools · footprint 12
3 med 8 low
Read AI
2 tools · footprint 12
2 med
SurveyMonkey
6 tools · footprint 12
2 med 4 low
Aurora MCP (Consilio)
4 tools · footprint 11
1 med 3 low
Google Sheets
3 tools · footprint 11
1 med 2 low
Harvey
5 tools · footprint 11
1 med 4 low
Honeycomb
10 tools · footprint 11
1 med 9 low
Intercom
13 tools · footprint 11
2 med 11 low
Microsoft Word (Work IQ)
4 tools · footprint 11
1 med 3 low
‹ PrevPage 15 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.