crossref-get-work

Fetch the full Crossref metadata record for a single DOI.

SERVERMeta Data Mcp SOURCEpypi:meta-data-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-derekslinz-meta-data-mcp/crossref-get-work.md

WHAT IT DOES

What crossref-get-work does on Meta Data Mcp

AI agents call crossref-get-work 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.

RISK

Why crossref-get-work is rated Low

This tool retrieves bibliographic metadata from Crossref using a DOI identifier. The verb 'Fetch' and the open data context confirm this is a read-only query operation that returns existing public metadata without creating, modifying, deleting, or executing any external operations.

From the tool's definition Tool name 'crossref-get-work' and description 'Fetch the full Crossref metadata record for a single DOI' indicate a retrieval operation with no modifications or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs crossref-get-work 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-get-work, this is the rule to start with:

crossref-get-work Allowed

crossref-get-work is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "crossref-get-work": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Meta Data Mcp, apply this rule, and every crossref-get-work call is checked against it from then on.

FAQ

Questions about crossref-get-work

What does the crossref-get-work tool do? +

Fetch the full Crossref metadata record for a single DOI. It is categorised as a Read tool in the Meta Data Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on crossref-get-work? +

Register the Meta Data MCP server in PolicyLayer and add a rule for crossref-get-work: 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.

What risk level is crossref-get-work? +

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

Can I rate-limit crossref-get-work? +

Yes. Add a rate_limit block to the crossref-get-work 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 crossref-get-work completely? +

Set action: deny in the PolicyLayer policy for crossref-get-work. 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 crossref-get-work? +

crossref-get-work 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.

KEEP EXPLORING

More on Meta Data, and thousands of servers like it.

This server

All 396 Meta Data tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →