crossref-works-by-title
Search Crossref works whose title field matches the given query.
This record as markdown: /tools/io-github-derekslinz-meta-data-mcp/crossref-works-by-title.md
What crossref-works-by-title does on Meta Data Mcp
AI agents call crossref-works-by-title 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-by-title is rated Low
This tool queries an open metadata API (Crossref) to retrieve bibliographic works matching a title search. It is a read-only operation that retrieves existing data without side effects, modifications, or irreversible actions. The low severity reflects minimal blast radius if misused — an AI agent could retrieve irrelevant or excessive metadata, but cannot harm systems or data integrity.
From the tool's definition Tool name contains 'search' and description states 'Search Crossref works whose title field matches the given query' — a pure query/retrieval operation with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
The rule that runs crossref-works-by-title 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-by-title, this is the rule to start with:
crossref-works-by-title 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-by-title call is checked against it from then on.
Questions about crossref-works-by-title
Search Crossref works whose title field matches the given query. 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-by-title: 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-by-title 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-by-title 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-by-title. 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-by-title 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