Low Risk

search_works_by_query

search_works_by_query

How to control search_works_by_query ↓

What search_works_by_query does on Crossref MCP Server

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

Low Risk

Why search_works_by_query needs a policy

This tool queries academic literature metadata from Crossref without side effects. Search operations are inherently Read category—they retrieve data for inspection without creating, modifying, or deleting anything. No financial transactions, code execution, or destructive actions are involved.

From the tool's definition Tool name 'search_works_by_query' indicates a search operation that retrieves academic literature data. Sibling tools (search_journals, search_funders, get_paper_metadata, get_work_metadata) are all Read operations that query the Crossref database without…

Documented attack patterns abuse exactly the kind of access search_works_by_query gives an agent:

How to control search_works_by_query

PolicyLayer is an MCP gateway — it sits between your AI agents and Crossref MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_works_by_query:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_works_by_query": {}
  }
}

search_works_by_query is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Crossref MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about search_works_by_query

What does the search_works_by_query tool do? +

search_works_by_query. It is categorised as a Read tool in the Crossref MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_works_by_query? +

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

What risk level is search_works_by_query? +

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

Can I rate-limit search_works_by_query? +

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

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

search_works_by_query is provided by the Crossref MCP Server MCP server (jackkuo666/crossref-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Crossref MCP Server tool call.

Start from Crossref MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

9 Crossref MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.