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
Apollo
4 tools · footprint 14
1 high 2 med 1 low
Asana
25 tools · footprint 14
5 med 20 low
ClickUp
25 tools · footprint 14
4 med 21 low
ClickUp
25 tools · footprint 14
4 med 21 low
Crossbeam
9 tools · footprint 14
4 med 5 low
Fireflies
3 tools · footprint 14
2 high 1 low
GitLab
15 tools · footprint 14
1 high 4 med 10 low COSOSOX
Google BigQuery
5 tools · footprint 14
1 high 4 low COSOSOX
Google Calendar
8 tools · footprint 14
5 med 3 low
Harmonic
7 tools · footprint 14
4 med 3 low
HubSpot CRM API
12 tools · footprint 14
4 med 8 low
HubSpot Meetings API
12 tools · footprint 14
4 med 8 low
Jira
14 tools · footprint 14
4 med 10 low
Microsoft Users (Work IQ)
6 tools · footprint 14
4 med 2 low
Otter.ai
3 tools · footprint 14
2 high 1 low
Pendo
15 tools · footprint 14
5 med 10 low
‹ PrevPage 13 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.