get_organization
Returns one organization's details: plan, your role, display count, allocated and remaining license slots. response_format 'detailed' adds the full member list (with roles) and display list. Use after list_organizations. Requires content scope and membership.
This record as markdown: /tools/de-agentview-agentview-mcp/get-organization.md
What get_organization does on agentView
AI agents call get_organization 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 |
|---|---|---|---|
org_id | string | Yes | Organization ID from list_organizations or get_account. |
access_token | string | — | Optional bearer token; prefer session_request_id. |
response_format | string | — | concise (default) returns counts and core fields; detailed adds members and displays arrays. |
session_request_id | string | — | Session handle from create_auth_session; pass it on every authenticated call. |
Parameters from the server's own tool schema.
Why get_organization is rated Low
Even though get_organization only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs get_organization 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 get_organization, this is the rule to start with:
get_organization 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 get_organization call is checked against it from then on.
Questions about get_organization
Returns one organization's details: plan, your role, display count, allocated and remaining license slots. response_format 'detailed' adds the full member list (with roles) and display list. Use after list_organizations. Requires content scope and membership. It is categorised as a Read tool in the agentView MCP Server, which means it retrieves data without modifying state.
get_organization accepts 4 parameters: org_id, access_token, response_format, session_request_id. Required: org_id. 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 get_organization: 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.
get_organization 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 get_organization 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 get_organization. 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.
get_organization 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