get_user_permissions

What get_user_permissions does on Claude MCP Server Ecosystem

AI agents call get_user_permissions to retrieve information from Claude MCP Server Ecosystem without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_user_permissions is rated Low

This tool retrieves permission information for a user. It performs no write, deletion, or execution operations. The severity is low because while permission data is sensitive, merely retrieving it for inspection poses minimal risk compared to tools that modify permissions, execute code, or delete resources. The read-only nature and informational purpose place it squarely in the Read category.

From the tool's definition Tool name 'get_user_permissions' and description 'Get all permissions for a user' indicate a retrieval operation. The verb 'get' is a standard read operation that queries and returns existing data without modifying, deleting, or executing any actions.

The rule that runs get_user_permissions safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude MCP Server Ecosystem, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_user_permissions, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_user_permissions": {}
  }
}

Questions about get_user_permissions