New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

crossref-datacitations.citations.browse

Browse article-to-dataset citation events by creation-date range and/or publisher member ID, without needing a known DOI. Useful for monitoring newly-deposited data citations from a specific publisher or time window. Data: api.crossref.org/beta/datacitations (CrossRef Data Citations API), no auth...

SERVERApibase SOURCEapibase-mcp-client
Low RISK CLASS
Category Read
Parameters 40 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/crossref-datacitations.citations.browse.md

What crossref-datacitations.citations.browse does on Apibase

AI agents call crossref-datacitations.citations.browse 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.

ParameterTypeRequiredDescription
rows integer — Number of citation events to return (1-500, default 20)
from_date string — Only citation events created on/after this date, YYYY-MM-DD or YYYY-MM-DDTHH:MM:SS (e.g. "2026-01-20")
member_id string — Filter to citing works from a specific CrossRef member/publisher ID (e.g. "78")
until_date string — Only citation events created on/before this date, YYYY-MM-DD or YYYY-MM-DDTHH:MM:SS (e.g. "2026-01-21")

Parameters from the server's own tool schema.

Why crossref-datacitations.citations.browse is rated Low

Tool queries and retrieves citation metadata without modification, creation, or deletion capabilities.

From the tool's definition Browse article-to-dataset citation events, no auth required, CC0 metadata

Questions about crossref-datacitations.citations.browse

What does the crossref-datacitations.citations.browse tool do? +

Browse article-to-dataset citation events by creation-date range and/or publisher member ID, without needing a known DOI. Useful for monitoring newly-deposited data citations from a specific publisher or time window. Data: api.crossref.org/beta/datacitations (CrossRef Data Citations API), no auth required, CC0 metadata, ~5-day delay between deposit and API appearance. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does crossref-datacitations.citations.browse accept? +

crossref-datacitations.citations.browse accepts 4 parameters: rows, from_date, member_id, until_date. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on crossref-datacitations.citations.browse? +

Register the Apibase MCP server in PolicyLayer and add a rule for crossref-datacitations.citations.browse: 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.

What risk level is crossref-datacitations.citations.browse? +

crossref-datacitations.citations.browse is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit crossref-datacitations.citations.browse? +

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

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

crossref-datacitations.citations.browse 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Apibase's. Pull the full record:

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.