When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance. Only omit if you're sure you don't need the data. Retrieve information about your current access token, including organization, environment, and permissions. Note that this can only b...
Part of the Mux MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call whoami_system_utilities to retrieve information from Mux without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though whoami_system_utilities only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
whoami_system_utilities:
rules:
- action: allowSee the full Mux policy for all 98 tools.
Agents calling read-class tools like whoami_system_utilities have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance. Only omit if you're sure you don't need the data. Retrieve information about your current access token, including organization, environment, and permissions. Note that this can only be access with an access token, and _all_ access tokens can access this route, regardless of what permissions they have assigned. # Response Schema ```json { $ref: '#/$defs/whoami_response', $defs: { whoami_response: { type: 'object', properties: { data: { type: 'object', properties: { access_token_name: { type: 'string' }, environment_id: { type: 'string' }, environment_name: { type: 'string' }, environment_type: { type: 'string' }, organization_id: { type: 'string' }, organization_name: { type: 'string' }, permissions: { type: 'array', items: { type: 'string' } } }, required: [ 'access_token_name', 'environment_id', 'environment_name', 'environment_type', 'organization_id', 'organization_name', 'permissions' ] } }, required: [ 'data' ] } } } ```. It is categorised as a Read tool in the Mux MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for whoami_system_utilities. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mux MCP server.
whoami_system_utilities is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the whoami_system_utilities rule in your Intercept policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the Intercept policy for whoami_system_utilities. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
whoami_system_utilities is provided by the Mux MCP server (@mux/mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept