list_organizations
Returns all organizations the authenticated user belongs to with their role, display count, member count and allocated slots. Use this to answer questions about the user's organizations, how many displays an organization has, or team membership. Requires authentication with at least content_only ...
This record as markdown: /tools/de-agentview-agentview-mcp/list-organizations.md
What list_organizations does on agentView
AI agents call list_organizations to retrieve information from agentView without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
access_token | string | — | Optional bearer token; prefer session_request_id. |
Parameters from the server's own tool schema.
Why list_organizations is rated Low
This tool queries and returns organizational metadata (role, display count, member count, allocated slots) without creating, modifying, or deleting any data. It is purely informational retrieval, fitting the Read category with low severity since the blast radius of misuse is limited to information disclosure of organizational structure.
From the tool's definition Tool name 'list_organizations' and description states it 'Returns all organizations' — a retrieval operation with no modification or side effects. Requires 'content_only' scope, indicating read-only access.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs list_organizations safely
PolicyLayer is an MCP gateway: it sits between your AI agents and agentView, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_organizations, this is the rule to start with:
list_organizations is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect agentView, apply this rule, and every list_organizations call is checked against it from then on.
Questions about list_organizations
Returns all organizations the authenticated user belongs to with their role, display count, member count and allocated slots. Use this to answer questions about the user's organizations, how many displays an organization has, or team membership. Requires authentication with at least content_only scope. It is categorised as a Read tool in the agentView MCP Server, which means it retrieves data without modifying state.
list_organizations accepts 1 parameter: access_token. The full parameter table on this page comes from the server's own tool schema.
Register the agentView MCP server in PolicyLayer and add a rule for list_organizations: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches agentView. Nothing to install.
list_organizations 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 list_organizations rule in your PolicyLayer 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 PolicyLayer policy for list_organizations. 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.
list_organizations is provided by the agentView MCP server (https://agentview.de/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on agentView, and thousands of servers like it.
This server
Across the catalogue