ror.organizations.get
Retrieve full details for a specific research organization from the Research Organization Registry (ROR) using its unique ROR identifier. Accepts the full URL format (https://ror.org/042nb2s44) or the short alphanumeric ID (042nb2s44). Returns comprehensive organization metadata including all nam...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/ror.organizations.get.md
What ror.organizations.get does on Apibase
AI agents call ror.organizations.get to retrieve information from Apibase 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 |
|---|---|---|---|
ror_id | string | Yes | ROR identifier for the organization. Accepts the full URL format (e.g. "https://ror.org/042nb2s44") or the short alphanumeric ID (e.g. "042nb2s44"). |
Parameters from the server's own tool schema.
Why ror.organizations.get is rated Low
Tool queries organizational metadata from ROR database with no side effects or data modification.
From the tool's definition Retrieve full details for a specific research organization from the Research Organization Registry
Attacks that exploit this kind of access
The rule that runs ror.organizations.get safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ror.organizations.get, this is the rule to start with:
ror.organizations.get 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 Apibase, apply this rule, and every ror.organizations.get call is checked against it from then on.
Questions about ror.organizations.get
Retrieve full details for a specific research organization from the Research Organization Registry (ROR) using its unique ROR identifier. Accepts the full URL format (https://ror.org/042nb2s44) or the short alphanumeric ID (042nb2s44). Returns comprehensive organization metadata including all name variants in multiple languages, organization type (Education, Funder, Healthcare, Company, Government, etc.), current status, founding year, primary location with coordinates, official website and Wikipedia URL, cross-registry identifiers (GRID, ISNI, Wikidata, FundRef), and parent/child/related organization relationships. Use after ror.organizations.search to get complete details for a found organization, or when you already know the ROR ID from scholarly metadata. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
ror.organizations.get accepts 1 parameter: ror_id. Required: ror_id. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for ror.organizations.get: 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 Apibase. Nothing to install.
ror.organizations.get 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 ror.organizations.get 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 ror.organizations.get. 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.
ror.organizations.get is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue