create_organization
Creates a new organization and makes the authenticated user the owner. Use this when the user wants to set up a shared display fleet. Returns orgId, name, slug, type and yourRole. Requires admin scope.
This record as markdown: /tools/de-agentview-agentview-mcp/create-organization.md
What create_organization does on agentView
AI agents use create_organization to create or update resources in agentView, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your agentView environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Friendly name for the organization. Example: 'Marketing Team'. |
type | string | — | Organization type. Defaults to 'organization' if omitted. |
access_token | string | — | Optional bearer token; prefer session_request_id. |
Parameters from the server's own tool schema.
Why create_organization is rated Medium
This is a Write-category tool because it creates and modifies data (new organization record) with reversible effects. It's not Destructive since organizations can be deleted/modified later.
From the tool's definition Tool creates a new organization entity and modifies system state by assigning the authenticated user as owner. Description states 'Creates a new organization' which is a create (write) operation. Requires admin scope indicating elevated permissions.
Risk signalsHandles credentials or secrets (access_token) · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs create_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 create_organization, this is the rule to start with:
create_organization stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 create_organization call is checked against it from then on.
Questions about create_organization
Creates a new organization and makes the authenticated user the owner. Use this when the user wants to set up a shared display fleet. Returns orgId, name, slug, type and yourRole. Requires admin scope. It is categorised as a Write tool in the agentView MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_organization accepts 3 parameters: name, type, access_token. Required: name. 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 create_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.
create_organization is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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