get_filterable_fields

Get a list of filterable field names and their types for a specified OpenAlex entity.

Server OpenAlex MCP Server reetp14/openalex-mcp
Category Read
Risk class Low
Parameters 00 required

What get_filterable_fields does on OpenAlex MCP Server

AI agents call get_filterable_fields to retrieve information from OpenAlex MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_filterable_fields needs a policy

This is a straightforward metadata retrieval operation that returns schema/field information about OpenAlex entities. It performs no data modification, deletion, external execution, or financial operations. The blast radius of misuse is minimal — an attacker gains only knowledge of available filter options, which is low-sensitivity metadata. Classification as Read is appropriate.

From the tool's definition Tool name 'get_filterable_fields' and description state it retrieves 'a list of filterable field names and their types' — a metadata query operation with no side effects, modifications, or code execution.

Questions about get_filterable_fields

What does the get_filterable_fields tool do? +

Get a list of filterable field names and their types for a specified OpenAlex entity. It is categorised as a Read tool in the OpenAlex MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_filterable_fields? +

Register the OpenAlex MCP Server MCP server in PolicyLayer and add a rule for get_filterable_fields: 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 OpenAlex MCP Server. Nothing to install.

What risk level is get_filterable_fields? +

get_filterable_fields is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_filterable_fields? +

Yes. Add a rate_limit block to the get_filterable_fields 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.

How do I block get_filterable_fields completely? +

Set action: deny in the PolicyLayer policy for get_filterable_fields. 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.

What MCP server provides get_filterable_fields? +

get_filterable_fields is provided by the OpenAlex MCP Server MCP server (reetp14/openalex-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.