Look up a single paper by its DOI. Returns full metadata
AI agents call search_by_doi to retrieve information from Q1 Crafter MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves bibliographic data from a DOI lookup service. It queries an external database and returns information without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an attacker could retrieve public academic metadata but cannot modify records, execute code, or cause harm. Classification as Read with low severity is appropriate.
From the tool's definition Tool description states 'Look up a single paper by its DOI. Returns full metadata' — a retrieval operation with no side effects. The verb 'look up' and the read-only nature of returning metadata confirm this is a query operation.
Attacks that exploit this kind of access
Look up a single paper by its DOI. Returns full metadata. It is categorised as a Read tool in the Q1 Crafter MCP MCP Server, which means it retrieves data without modifying state.
Register the Q1 Crafter MCP server in PolicyLayer and add a rule for search_by_doi: 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 Q1 Crafter MCP. Nothing to install.
search_by_doi 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 search_by_doi 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 search_by_doi. 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.
search_by_doi is provided by the Q1 Crafter MCP server (muslus/q1-crafter-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →