figshare.taxonomy.categories
Browse or search Figshare's subject taxonomy (2000+ categories, e.g. "Ecohydrology", "Agricultural biotechnology") used to classify research articles. Optionally filter by a free-text title query. Returns category id, title, parent_id, and taxonomy path — useful for understanding how Figshare org...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/figshare.taxonomy.categories.md
What figshare.taxonomy.categories does on Apibase
AI agents call figshare.taxonomy.categories 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 |
|---|---|---|---|
limit | integer | — | Max categories to return (default 50, max 200). |
query | string | — | Optional free-text filter on category/subject title (e.g. "ecology", "biotechnology"). Omit to browse the full taxonomy. |
Parameters from the server's own tool schema.
Why figshare.taxonomy.categories is rated Low
Tool retrieves and queries taxonomy metadata without modifying data or executing operations.
From the tool's definition Browse or search Figshare's subject taxonomy, returns category id, title, parent_id
Attacks that exploit this kind of access
The rule that runs figshare.taxonomy.categories 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 figshare.taxonomy.categories, this is the rule to start with:
figshare.taxonomy.categories 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 figshare.taxonomy.categories call is checked against it from then on.
Questions about figshare.taxonomy.categories
Browse or search Figshare's subject taxonomy (2000+ categories, e.g. "Ecohydrology", "Agricultural biotechnology") used to classify research articles. Optionally filter by a free-text title query. Returns category id, title, parent_id, and taxonomy path — useful for understanding how Figshare organizes research by subject area. Data: Figshare.com, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
figshare.taxonomy.categories accepts 2 parameters: limit, query. 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 figshare.taxonomy.categories: 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.
figshare.taxonomy.categories 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 figshare.taxonomy.categories 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 figshare.taxonomy.categories. 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.
figshare.taxonomy.categories 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