ror.organizations.affiliation
Intelligently match a free-text affiliation string (as found in academic paper bylines or grant records) to research organizations in the ROR registry. Pass the raw affiliation text exactly as it appears — e.g. "Dept. of Physics, Univ. of California, Berkeley, CA, USA" or "Max-Planck-Institut für...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/ror.organizations.affiliation.md
What ror.organizations.affiliation does on Apibase
AI agents call ror.organizations.affiliation 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 |
|---|---|---|---|
affiliation | string | Yes | Free-text affiliation string to match against the ROR registry, as it appears in an academic paper or grant record (e.g. "Dept. of Physics, Univ. of California, |
Parameters from the server's own tool schema.
Why ror.organizations.affiliation is rated Low
Queries a registry to identify matching organizations; returns data without modifying records or executing code.
From the tool's definition Intelligently match affiliation string to research organizations in ROR registry. Returns candidates with confidence score.
Attacks that exploit this kind of access
The rule that runs ror.organizations.affiliation 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.affiliation, this is the rule to start with:
ror.organizations.affiliation 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.affiliation call is checked against it from then on.
Questions about ror.organizations.affiliation
Intelligently match a free-text affiliation string (as found in academic paper bylines or grant records) to research organizations in the ROR registry. Pass the raw affiliation text exactly as it appears — e.g. "Dept. of Physics, Univ. of California, Berkeley, CA, USA" or "Max-Planck-Institut für Astronomie, Heidelberg". ROR's affiliation matching algorithm performs substring detection, name-variant lookup, and scoring to identify candidate organizations. Returns each candidate with: confidence score (0–1), a "chosen" boolean (the best single match), matching_type (e.g. SINGLE SEARCH, COMMON TERMS), and the organization's ROR ID, canonical name, type, and country. Ideal for metadata curation, ORCID affiliation disambiguation, funder acknowledgment normalization, and building organization-level research analytics from unstructured text. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
ror.organizations.affiliation accepts 1 parameter: affiliation. Required: affiliation. 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.affiliation: 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.affiliation 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.affiliation 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.affiliation. 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.affiliation 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