crossref-works-search
Search Crossref scholarly works with full-text query, filters, sort, and field selection.
This record as markdown: /tools/io-github-derekslinz-meta-data-mcp/crossref-works-search.md
What crossref-works-search does on Meta Data Mcp
AI agents call crossref-works-search to retrieve information from Meta Data Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why crossref-works-search is rated Low
This tool retrieves and queries scholarly metadata from the Crossref database. It has no side effects, does not modify data, execute code, delete records, or trigger external operations. The search, filter, and sort parameters are all read operations. The blast radius of misuse is minimal — an agent could only retrieve excess data or perform resource-intensive queries, not cause harm.
From the tool's definition Tool performs search operations on Crossref scholarly works with "full-text query, filters, sort, and field selection" — all read-only query operations with no data modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs crossref-works-search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Data Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crossref-works-search, this is the rule to start with:
crossref-works-search 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 Meta Data Mcp, apply this rule, and every crossref-works-search call is checked against it from then on.
Questions about crossref-works-search
Search Crossref scholarly works with full-text query, filters, sort, and field selection. It is categorised as a Read tool in the Meta Data Mcp MCP Server, which means it retrieves data without modifying state.
Register the Meta Data MCP server in PolicyLayer and add a rule for crossref-works-search: 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 Meta Data Mcp. Nothing to install.
crossref-works-search 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 crossref-works-search 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 crossref-works-search. 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.
crossref-works-search is provided by the Meta Data MCP server (pypi:meta-data-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Data, and thousands of servers like it.
This server
Across the catalogue