ror.organizations.filter
Filter the Research Organization Registry (ROR) by organization type, country, and/or status to browse subsets of the 110,000+ global research organizations. Supports combining multiple filters with an optional keyword query. Organization types include: Education (universities, colleges), Healthc...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/ror.organizations.filter.md
What ror.organizations.filter does on Apibase
AI agents call ror.organizations.filter 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 |
|---|---|---|---|
page | integer | — | Page number for pagination (1-indexed, default 1). Each page returns up to 20 results. |
query | string | — | Optional keyword query to narrow results within the filter. Combines with type/country/status filters. |
types | string | — | Filter by organization type. Valid values: Education, Healthcare, Company, Archive, Nonprofit, Government, Facility, Funder, Other (e.g. "Education" returns uni |
status | string | — | Organization status filter. Valid values: active (default), inactive, withdrawn. Use "inactive" or "withdrawn" to include legacy records. |
country_code | string | — | ISO 3166-1 alpha-2 country code to filter organizations by country (e.g. "US", "DE", "GB", "JP"). |
Parameters from the server's own tool schema.
Why ror.organizations.filter is rated Low
Tool queries and retrieves data from ROR registry without side effects or modifications.
From the tool's definition Filter, browse, query research organizations; no modification or execution.
Attacks that exploit this kind of access
The rule that runs ror.organizations.filter 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.filter, this is the rule to start with:
ror.organizations.filter 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.filter call is checked against it from then on.
Questions about ror.organizations.filter
Filter the Research Organization Registry (ROR) by organization type, country, and/or status to browse subsets of the 110,000+ global research organizations. Supports combining multiple filters with an optional keyword query. Organization types include: Education (universities, colleges), Healthcare (hospitals, clinics), Company (industry research), Archive (data repositories, libraries), Nonprofit (NGOs, foundations), Government (agencies, national labs), Facility (research infrastructures, telescopes), Funder (grant agencies, funding bodies), and Other. Country is specified as ISO 3166-1 alpha-2 code (US, DE, GB, JP, CN, etc.). Returns total match count and up to 20 results per page with name, type, status, country, city, and website. Useful for generating lists of institutions in a specific country, enumerating funders by country, or counting research organizations by type. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
ror.organizations.filter accepts 5 parameters: page, query, types, status, country_code. 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.filter: 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.filter 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.filter 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.filter. 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.filter 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